]> git.lizzy.rs Git - rust.git/commit
projects / rust.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(merge: 72599c6 b83078f)
Rollup merge of #107631 - BoxyUwU:triagebot_cargo_lock, r=compiler-errors
authorMichael Goulet <michael@errs.io>
Fri, 3 Feb 2023 22:15:24 +0000 (14:15 -0800)
committerGitHub <noreply@github.com>
Fri, 3 Feb 2023 22:15:24 +0000 (14:15 -0800)
commitef520bd82a43caed2bd28f05d8dd29a74d23ba04
tree424e6d660cf25e8e7e875b414e525cf4cbcdb951tree | snapshot
parent72599c69b5db0ea87a843d6f546af1d10ded34a1commit | diff
parentb83078fd7108972ce56263278a515d62e5f35ee2commit | diff
Rollup merge of #107631 - BoxyUwU:triagebot_cargo_lock, r=compiler-errors

loudly tell people when they change `Cargo.lock`

It keeps happening that people accidentally commit changes to `Cargo.lock` and then have to be told by a reviewer to undo this. I've also seen cases where PRs are merged that accidentally changed `Cargo.lock` during a rebase.. I figure that purposeful changes to `Cargo.lock` are likely rarer than these accidental ones?
triagebot.toml diff1 | diff2 | blob | history
Empowering everyone to build reliable and efficient software.