Repository navigation
Don't cc rust-lang/compiler for toolstate changes #65238
Copy link
Copy link
Closed
Labels
C-enhancementCategory: An issue proposing an enhancement or a PR with one.Category: An issue proposing an enhancement or a PR with one.E-easyCall for participation: Easy difficulty. Experience needed to fix: Not much. Good first issue.Call for participation: Easy difficulty. Experience needed to fix: Not much. Good first issue.T-compilerRelevant to the compiler team, which will review and decide on the PR/issue.Relevant to the compiler team, which will review and decide on the PR/issue.T-dev-toolsRelevant to the dev-tools subteam, which will review and decide on the PR/issue.Relevant to the dev-tools subteam, which will review and decide on the PR/issue.T-infraRelevant to the infrastructure team, which will review and decide on the PR/issue.Relevant to the infrastructure team, which will review and decide on the PR/issue.
Description
While it's important to keep on top of regressions to the toolstate, most of the time these issues are fixed quickly, by the author of the PR that caused the regression, or someone else. With GitHub notifications being difficult enough to keep up with as it is, being mentioned on every toolstate change issue is mostly noise. The issues are already tagged T-compiler and nominated, so I think additionally pinging everyone is unnecessary.
I think it would be sensible to change:
rust/src/tools/publish_toolstate.py
Line 146 in 5283791
| cc @{}, the PR reviewer, and @rust-lang/compiler -- nominating for prioritization. |
to:
cc @{}, the PR reviewer, and nominating for compiler team prioritization.
cc @rust-lang/compiler
Reacted by Esteban Kuber, Phil Hansch, Mazdak Farrokhzad, Yuki Okushi and Bogdan Arabadzhi
Metadata
Metadata
Assignees
Labels
C-enhancementCategory: An issue proposing an enhancement or a PR with one.Category: An issue proposing an enhancement or a PR with one.E-easyCall for participation: Easy difficulty. Experience needed to fix: Not much. Good first issue.Call for participation: Easy difficulty. Experience needed to fix: Not much. Good first issue.T-compilerRelevant to the compiler team, which will review and decide on the PR/issue.Relevant to the compiler team, which will review and decide on the PR/issue.T-dev-toolsRelevant to the dev-tools subteam, which will review and decide on the PR/issue.Relevant to the dev-tools subteam, which will review and decide on the PR/issue.T-infraRelevant to the infrastructure team, which will review and decide on the PR/issue.Relevant to the infrastructure team, which will review and decide on the PR/issue.
Activity
michaelwoerister commentedon Oct 9, 2019
I think that's a good idea!
nikomatsakis commentedon Oct 9, 2019
I agree that the pings are rarely useful. Nominating is probably sufficient.
Rollup merge of rust-lang#65276 - varkor:toolstate-no-ping, r=Mark-Si…
Rollup merge of rust-lang#65276 - varkor:toolstate-no-ping, r=Mark-Si…
Rollup merge of rust-lang#65276 - varkor:toolstate-no-ping, r=Mark-Si…
Rollup merge of rust-lang#65276 - varkor:toolstate-no-ping, r=Mark-Si…