Skip to content

Conversation

@jieyouxu
Copy link
Member

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-triage This 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.

The [relabel] section with needs-triage This issue or PR needs triaging to determine its status. Remove label once sufficiently triaged. as allow-unauthenticated will allow users without write access to this repo to remove the needs-triage This issue or PR needs triaging to determine its status. Remove label once sufficiently triaged. label through @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.

@jieyouxu jieyouxu added the A-meta Area: meta (e.g. triagebot configuration) label Oct 30, 2025
@Manishearth Manishearth merged commit ae9e327 into rust-lang:master Oct 30, 2025
26 checks passed
@jieyouxu jieyouxu deleted the needs-triage branch October 30, 2025 16:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

A-meta Area: meta (e.g. triagebot configuration)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants