Tracking issue for reorganizing labels in the rustfmt repo
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 7k
- Forks
- 1.1k
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 24
Description
Context: #t-rustfmt > Triage labels. We should do a survey pass of open issues and PRs to assess current situation. This is the subtask of assessing and reorganizing what labels we have, to make triaging easier.
[!WARNING]
Work-in-progress, will be continuously updated.
Planned reorganizations
- Introduce a
F-*(expected impact on formatting output and configuration) family of labels.- https://github.com/rust-lang/rustfmt/labels/F-impacts-default-format-config
- https://github.com/rust-lang/rustfmt/labels/F-impacts-stable-formatted-code
- https://github.com/rust-lang/rustfmt/labels/F-impacts-stable-unformatted-code
- https://github.com/rust-lang/rustfmt/labels/F-impacts-unstable-code
- https://github.com/rust-lang/rustfmt/labels/F-no-formatting-impact
- https://github.com/rust-lang/rustfmt/labels/F-untriaged-formatting-impact
- Introduce a
C-*("category") family of labels (mirroring r-l/r) for categorizing issue kinds. - Introduce a
B-*("blocked") family of labels to split https://github.com/rust-lang/rustfmt/labels/blocked more specific block reasons.- https://github.com/rust-lang/rustfmt/labels/B-prerequisite-rustc-changes
- https://github.com/rust-lang/rustfmt/labels/B-has-concerns (FIXME:
S-has-concerns) - https://github.com/rust-lang/rustfmt/labels/B-prerequisite-changes
- https://github.com/rust-lang/rustfmt/labels/B-needs-style-edition-gate
- https://github.com/rust-lang/rustfmt/labels/B-t-style-decision
- Introduce
I-*("indicator"/"important") family of labels (not intended to fully mirror r-l/r):I-lang-stabilization(for lang feature stabilizations),I-rustfmt-nominated(for rustfmt team discussion) - Check if we can use
S-waiting-on-{author,reviewer}binary label like r-l/r instead ofpr-{not-reviewed,follow-up-review-pending}+s-waiting-on-author. - Split https://github.com/rust-lang/rustfmt/labels/pr-on-hold into more specific reasons. (Survey what the common reasons are first.)
- Mirror https://github.com/rust-lang/rustfmt/labels/needs-rfc
Planned cleanups
- Reassess current area
A-*family of labels.
Other tasks
- Document label families as part of issue / PR triaging in https://github.com/rust-lang/rustfmt/issues/6686.
- Investigate how priorities are determined, and if
P-*family of labels have different meanings for issues vs PRs. - Investigate https://github.com/rust-lang/rustfmt/labels/community%20driven label.
- Investigate https://github.com/rust-lang/rustfmt/labels/help%20wanted label.
Remarks on current labels
Pending.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked Zulip discussion and the current GitHub label list, then review the open issues and PRs referenced by the planned reorganizations. Track which label families and investigations remain incomplete; the work is done when the survey, label cleanup, and any linked triage documentation tasks have clear conclusions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, rust
- Domain
- documentation, tooling
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100