Labels

Lowest priority. Possibly useful, but not yet enough support to actually get it done.

Higher priority than priority/awaiting-more-evidence.

Highest priority. Must be actively worked on as someone's top priority right now.

Important over the long term, but may not be staffed and/or may need multiple releases to complete.

Must be staffed and worked on either currently, or very soon, ideally in time for the next release.

Signifies that Product Support has signed off on this PR

Signifies that QE has signed off on this PR

Indicates a PR has been reviewed by automated tools and is ready for human review

Indicates the PR should not be rebased by the rebasebot.

Denotes a PR that will be considered when it comes time to generate release notes.

Denotes a PR that introduces potentially breaking changes that require user action.

Denotes a PR that doesn't merit a release note.

Categorizes an issue as related to the Product Reliability Agent.

Denotes a PR that changes 100-499 lines, ignoring generated files.

Denotes a PR that changes 30-99 lines, ignoring generated files.

Denotes a PR that changes 10-29 lines, ignoring generated files.

Denotes a PR that changes 500-999 lines, ignoring generated files.

Denotes a PR that changes 0-9 lines, ignoring generated files.

Denotes a PR that changes 1000+ lines, ignoring generated files.

Indicates that the PR approves the stability in a repo

Indicates a release branch PR has been approved by a staff engineer (formerly group/pillar lead).

Denotes an issue that blocks the tide merge queue for a branch while it is open.

Denotes a PR that should use a standard merge by tide when it merges.

Denotes a PR that should be rebased by tide when it merges.