Indicates a PR has been approved by an approver from all required OWNERS files.
Indicates that a PR should not merge because it touches files in blocked paths.
Indicates that a PR is not yet approved to merge into a release branch.
Indicates that a PR should not merge because someone has issued a /hold command.
Indicates that a PR should not merge because it has an invalid OWNERS file in it.
Indicates that a PR should not merge because it's missing one of the release note labels.
Indicates that a PR should not merge because it is a work in progress.
DEPRECATED. Indicates that a PR should not merge. Label can only be manually applied/removed.
This issue or pull request already exists
Extra attention is needed
Categorizes issue or PR as related to a bug.
Categorizes issue or PR as related to cleanup.
Categorizes issue or PR as related to documentation.
Categorizes issue or PR as related to a new feature.
Categorizes issue or PR as related to test flakes.
Indicates that a PR is ready to be merged.
Indicates that an issue or PR should not be auto-closed due to staleness.
Denotes an issue or PR that has aged beyond lifecycle/stale and will be auto-closed.
Denotes an issue or PR has remained open with no activity for too long and has become stale.
Indicates a PR that requires an org member to verify it is safe to test.
Indicates a PR cannot be merged because it has merge conflicts with HEAD.
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.