Issues or PRs related to tracing
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 commit message.
Indicates that a PR should not merge because it has an invalid OWNERS file in it.
Indicates that a PR should not merge beacuse it has missing documentation review.
Indicates that a PR should not merge because it is a work in progress.
Improvements or additions to documentation
This issue or pull request already exists
Denotes an issue ready for a new contributor, according to the "help wanted" guidelines.
Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.
Categorizes issue or PR as related to a bug.
Categorizes issue or PR as related to cleaning up code, process, or technical debt.
Categorizes issue or PR as related to a feature/enhancement marked for deprecation.
Categorizes issue or PR as related to a consistently or frequently failing test.
Categorizes issue or PR as related to a new feature.
Categorizes issue or PR as related to a flaky test.
Categorizes issue or PR as related to missing automated tests for scenario.
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.
Denotes a PR that is trusted and should be build.
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.