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.
Indicates an issue or PR lacks a `triage/...` label and requires one.
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.
Issues or PRs related to Adviser
Categorizes an issue or PR as relevant to SIG Cyborgs and Bots.
Categorizes an issue or PR as relevant to SIG DevSecOps.
Categorizes an issue or PR as relevant to SIG Docs.
Issues or PRs related to {meta\|performance\|security} indicators.