Skip to content

labels.md

Latest commit

 

History

History
33 lines (26 loc) · 1.58 KB

labels.md

File metadata and controls

33 lines (26 loc) · 1.58 KB

Labels used in the team repository

Some labels are setup to make it easier to figure out the status of an issue or PR, and allows contributors to filter issues/PRs by labels.

Labels are currently manually applied

triagebot is not currently set up for the team repository with write access (which needs to be tightly controlled). Thus, labels are currently manually applied and adjusted. See threat model.

Meaning of labels

  • needs-{team-repo,infra}-admin-review: needs one of the infra-admins or team-repo-admins or one from both to review (and approve/reject).
  • needs-team-lead-review: needs a relevant team or Working Group (WG) or Project Group (PG) lead to approve.
  • Statuses:
    • S-waiting-on-{author,review,team}: self-evident
    • S-has-concerns: outstanding concerns that must be addressed
    • S-blocked: blocked on something
  • Team labels: only T-{infra,leadership-council}, the latter is intended to help council members to see what team PRs would need Council feedback or concerns the Council somehow.
  • E-{easy,medium,hard} and E-help-wanted: call-for-participation labels copied from rust-lang/rust.
  • needs-triage: someone should try to figure out what the issue/PR needs/is/affects/is blocked on.
  • needs-council-fcp: something that requires the Council to FCP (outside team repo as rfcbot isn't enabled).