diff options
| author | Michael Goulet <michael@errs.io> | 2023-02-03 14:15:24 -0800 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2023-02-03 14:15:24 -0800 |
| commit | ef520bd82a43caed2bd28f05d8dd29a74d23ba04 (patch) | |
| tree | 424e6d660cf25e8e7e875b414e525cf4cbcdb951 | |
| parent | 72599c69b5db0ea87a843d6f546af1d10ded34a1 (diff) | |
| parent | b83078fd7108972ce56263278a515d62e5f35ee2 (diff) | |
| download | rust-ef520bd82a43caed2bd28f05d8dd29a74d23ba04.tar.gz rust-ef520bd82a43caed2bd28f05d8dd29a74d23ba04.zip | |
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?
| -rw-r--r-- | triagebot.toml | 8 |
1 files changed, 8 insertions, 0 deletions
diff --git a/triagebot.toml b/triagebot.toml index 9e37eccb6d3..d54d80c5adb 100644 --- a/triagebot.toml +++ b/triagebot.toml @@ -460,6 +460,14 @@ These commits modify **compiler targets**. [mentions."src/doc/style-guide"] cc = ["@rust-lang/style"] +[mentions."Cargo.lock"] +message = """ +These commits modify the `Cargo.lock` file. Random changes to `Cargo.lock` can be introduced when switching branches and rebasing PRs. +This was probably unintentional and should be reverted before this PR is merged. + +If this was intentional then you can ignore this comment. +""" + [assign] warn_non_default_branch = true contributing_url = "https://rustc-dev-guide.rust-lang.org/contributing.html" |