Begin labelling new issues with needs-triage
#6716
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Part of #t-rustfmt > Triage labels.
The main motivation here is to distinguish between issues that have not received any triaging (not even an initial pass), versus issues that have. It's intended that the needs-triageThis issue or PR needs triaging to determine its status. Remove label once sufficiently triaged.
label will be removed once a team member or contributor has performed an initial triage on the issue.
Triage docs and label docs are intended as follow-ups, since I still need to investigate how to effectively triage rustfmt issues and PRs.
TheThis issue or PR needs triaging to determine its status. Remove label once sufficiently triaged.
as This issue or PR needs triaging to determine its status. Remove label once sufficiently triaged.
label through
[relabel]section with needs-triageallow-unauthenticatedwill allow users without write access to this repo to remove the needs-triage@rustbot label: -needs-triage. There are other labels that should also go in here, but left as a follow-up PR to restrict scope of this PR.