Skip to content

Labels

Labels

  • Indicates a PR has been approved by an approver from all required OWNERS files.
  • Indicates that a PR should not merge because someone has issued a /hold command.
  • Indicates that a PR should not merge because it's missing one of the release note labels.
  • 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
  • New feature or request
  • Good for newcomers
  • Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.
  • This doesn't seem right
  • 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 design.
  • Categorizes issue or PR as related to documentation.
  • Categorizes issue or PR as related to enhancement.
  • 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 new api.
  • Categorizes issue or PR as related to support.
  • Categorizes issue or PR as related to technical debt.
  • Categorizes issue or PR as related to a consistently or frequently failing test.
  • Categorizes issue or PR as related to upstream.
  • Indicates that a PR is ready to be merged.
  • 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.
  • Highest priority. Must be actively worked on as someone's top priority right now.