Labels
Labels
31 labels
- Indicates PR includes api change.
- Indicates a PR has been approved by an approver from all required OWNERS files.
- Lowest priority. Possibly useful, but not yet enough support to actually get it done.
- Higher priority than priority/awaiting-more-evidence.
- Categorizes issue or PR as related to a bug.
- Categorizes issue or PR as related to cleaning up code, process, or technical debt.
- Pull requests that update a dependency file
- Indicates that a PR should not merge because someone has issued a /hold command.
- Indicates a PR lacks a label and requires one.
- Indicates that a PR should not merge because it is a work in progress.
- Categorizes issue or PR as related to documentation.
- This issue or pull request already exists
- Categorizes issue or PR as related to a new feature with API changes.
- Categorizes issue or PR as related to a consistently or frequently failing test.
- Categorizes issue or PR as related to a new feature.
- Pull requests that update go code
- Good for newcomers
- Extra attention is needed
- 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.
- This doesn't seem right
- Looks good to me, indicates that a PR is ready to be merged.
- Indicates a PR lacks a label and requires one.
- Indicates a PR lacks a label and requires one.
- Indicates an issue or PR lacks a label and requires one.
- Further information is requested
- Categorizes issue or PR as related to support.
- Indicates an issue or PR is ready to be actively worked on.
- Indicates an issue needs more information in order to work on it.