Labels

• approved

  Indicates a PR has been approved by an approver from all required OWNERS files.
• dependencies

  Pull requests that update a dependency file
• deprecated

  This is a set of deprecated labels, they will be removed
• do-not-merge/blocked-paths

  Indicates that a PR should not merge because it touches files in blocked paths.
• do-not-merge/hold

  Indicates that a PR should not merge because someone has issued a /hold command.
• do-not-merge/invalid-owners-file

  Indicates that a PR should not merge because it has an invalid OWNERS file in it.
• do-not-merge/work-in-progress

  Indicates that a PR should not merge because it is a work in progress.
• documentation

  Improvements or additions to documentation
• duplicate

  This issue or pull request already exists
• good first issue

  Good for newcomers
• hacktoberfest

  Issues targeting the hacktoberfest participants.
• hacktoberfest-accepted

  PR that has been accepted for hacktoberfest!
• help wanted

  Extra attention is needed
• invalid

  This doesn't seem right
• kind/bug

  Categorizes issue or PR as related to a bug.
• kind/cleanup

  Categorizes issue or PR as related to cleaning up code, process, or technical debt.
• kind/deprecation

  Categorizes issue or PR as related to a feature/enhancement marked for deprecation.
• kind/documentation

  Categorizes issue or PR as related to documentation.
• kind/feature

  Categorizes issue or PR as related to a new feature.
• kind/question

  Categorizes issue or PR as a support question.
• lgtm

  Indicates that a PR is ready to be merged.
• lifecycle/active

  Indicates that an issue or PR is actively being worked on by a contributor.
• lifecycle/frozen

  Indicates that an issue or PR should not be auto-closed due to staleness.
• lifecycle/rotten

  Denotes an issue or PR that has aged beyond stale and will be auto-closed.
• lifecycle/stale

  Denotes an issue or PR has remained open with no activity and has become stale.
• needs-ok-to-test

  Indicates a PR that requires an org member to verify it is safe to test.
• needs-rebase

  Indicates a PR cannot be merged because it has merge conflicts with HEAD.
• priority/awaiting-more-evidence

  Lowest priority. Possibly useful, but not yet enough support to actually get it done.
• priority/backlog

  Higher priority than priority/awaiting-more-evidence.
• priority/critical-urgent

  Highest priority. Must be actively worked on as someone's top priority right now.