Indicates a PR has been approved by an approver from all required OWNERS files.
This Issue or PR is related to a specific deployment.
This Issue or PR is related to a specific deployment.
This Issue or PR is related to a specific deployment.
Indicates that a PR should not merge because it touches files in blocked paths.
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 is a work in progress.
Improvements or additions to documentation
Issues targeting the hacktoberfest participants.
PR that has been accepted for hacktoberfest!
Extra attention is needed
Categorizes issue or PR as related to a bug.
Categorizes issue or PR as related to cleaning up code, process, or technical debt.
This is an Issue or PR someone want to give a demo or request a demo.
Categorizes issue or PR as related to a feature/enhancement marked for deprecation.
Categorizes issue or PR as related to documentation.
Categorizes issue or PR as related to a new feature.
Categorizes issue or PR as a support question.
Indicates that a PR is ready to be merged.
Indicates that an issue or PR is actively being worked on by a contributor.
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 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.