Labels
Labels
120 labels
- Categorizes issue or PR as related to adding, removing, or otherwise changing an API
- 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 design.
- Categorizes issue or PR as related to documentation.
- 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 a regression from a prior release.
- Categorizes issue or PR as a support question.
- "Looks good to me", 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 lacks a `kind/foo` label and requires one.
- 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 `sig/foo` label and requires one.
- Indicates an issue or PR lacks a `triage/foo` label and requires one.
- 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.
- 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.
- 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.