X-Git-Url: https://git.lizzy.rs/?a=blobdiff_plain;f=triagebot.toml;h=ba9ed20cc64a2a271404bd005279b751be672b23;hb=f2a1e45246be1564a137db77d655e53fa3dc0759;hp=8aefb1f620b3d62b90a5d84a2f6df46cb4f6bba0;hpb=ec8477fea1989bb187ec026b2dad3e4b89d60e91;p=rust.git diff --git a/triagebot.toml b/triagebot.toml index 8aefb1f620b..ba9ed20cc64 100644 --- a/triagebot.toml +++ b/triagebot.toml @@ -219,7 +219,7 @@ changelog-branch = "master" [mentions."compiler/rustc_apfloat"] message = """ -Changes rustc_apfloat. rustc_apfloat is currently in limbo and you almost +Changes rustc_apfloat. rustc_apfloat is currently in limbo and you almost \ certainly don't want to change it (see #55993). """ cc = ["@eddyb"] @@ -244,7 +244,7 @@ cc = ["@rust-lang/miri"] [mentions."compiler/rustc_mir_transform/src/"] message = "Some changes occurred to MIR optimizations" -cc = ["@rust-lang/mir-opt"] +cc = ["@rust-lang/wg-mir-opt"] [mentions."compiler/rustc_trait_selection/src/traits/const_evaluatable.rs"] message = "Some changes occurred in const_evaluatable.rs" @@ -258,22 +258,22 @@ cc = ["@GuillaumeGomez"] message = """ Hey! It looks like you've submitted a new PR for the library teams! -If this PR contains changes to any `rust-lang/rust` public library APIs then -please comment with `@rustbot label +T-libs-api -T-libs` to tag it -appropriately. If this PR contains changes to any unstable APIs please edit -the PR description to add a link to the relevant [API Change -Proposal](https://std-dev-guide.rust-lang.org/feature-lifecycle/api-change-proposals.html) -or [create one](https://github.com/rust-lang/libs-team/issues/new?assignees=&labels=api-change-proposal%2C+T-libs-api&template=api-change-proposal.md&title=%28My+API+Change+Proposal%29) -if you haven't already. If you're unsure where your change falls no worries, -just leave it as is and the reviewer will take a look and make a decision to +If this PR contains changes to any `rust-lang/rust` public library APIs then \ +please comment with `@rustbot label +T-libs-api -T-libs` to tag it \ +appropriately. If this PR contains changes to any unstable APIs please edit \ +the PR description to add a link to the relevant [API Change \ +Proposal](https://std-dev-guide.rust-lang.org/feature-lifecycle/api-change-proposals.html) \ +or [create one](https://github.com/rust-lang/libs-team/issues/new?assignees=&labels=api-change-proposal%2C+T-libs-api&template=api-change-proposal.md&title=%28My+API+Change+Proposal%29) \ +if you haven't already. If you're unsure where your change falls no worries, \ +just leave it as is and the reviewer will take a look and make a decision to \ forward on if necessary. Examples of `T-libs-api` changes: * Stabilizing library features -* Introducing insta-stable changes such as new implementations of existing +* Introducing insta-stable changes such as new implementations of existing \ stable traits on existing stable types -* Introducing new or changing existing unstable library APIs (excluding +* Introducing new or changing existing unstable library APIs (excluding \ permanently unstable features / features without a tracking issue) * Changing public documentation in ways that create new stability guarantees * Changing observable runtime behavior of library APIs @@ -300,8 +300,8 @@ cc = ["@Cldfire"] [mentions."src/rustdoc-json-types"] message = """ -rustdoc-json-types is a **public** (although nightly-only) API. -If possible, consider changing `src/librustdoc/json/conversions.rs`; +rustdoc-json-types is a **public** (although nightly-only) API. \ +If possible, consider changing `src/librustdoc/json/conversions.rs`; \ otherwise, make sure you bump the `FORMAT_VERSION` constant. """ cc = [ @@ -316,7 +316,12 @@ cc = ["@ehuss"] cc = ["@rust-lang/clippy"] [mentions."src/tools/miri"] +message = "The Miri submodule was changed" cc = ["@rust-lang/miri"] [mentions."src/tools/rustfmt"] cc = ["@rust-lang/rustfmt"] + +[mentions."compiler/rustc_middle/src/mir/syntax.rs"] +message = "This PR changes MIR" +cc = ["@oli-obk", "@RalfJung", "@JakobDegen", "@davidtwco", "@celinval"]