Indicates that an issue or PR should not be auto-closed due to staleness.
Denotes an issue or PR that has aged beyond stale and will be auto-closed.
Denotes an issue or PR has remained open with no activity and has become stale.
Indicates that a PR requires a review from an approver.
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.
Indicates a non-member PR verified by an org member that is safe to test.
Lowest priority. Possibly useful, but not yet enough support to actually get it done.
Indicate that the issue or PR is a lower priority and can be worked on in the future
Categorizes an issue or pull request as critical and of urgent priority.
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.
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.
Denotes an issue or PR that relates to changes in api.
Denotes an issue or PR that relates to changes in the build system.
Denotes an issue or PR as being related to sig-ci, marks changes to the CI system.
Denotes an issue or PR that relates to observability.