Labels

• do-not-merge/cherry-pick-not-approved

  Indicates that a PR is not yet approved to merge into a release branch.
• do-not-merge/hold

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

  Indicates that a PR should not merge because it has an invalid commit message.
• 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/release-note-label-needed

  Indicates that a PR should not merge because it's missing one of the release note labels.
• 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
• go

  Pull requests that update Go code
• good first issue

  Denotes an issue ready for a new contributor, according to the "help wanted" guidelines.
• help wanted

  Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.
• kind/api-change

  Categorizes issue or PR as related to adding, removing, or otherwise changing an API
• 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/design

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

  Categorizes issue or PR as related to documentation.
• kind/failing-test

  Categorizes issue or PR as related to a consistently or frequently failing test.
• kind/feature

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

  Categorizes issue or PR as related to a flaky test.
• kind/proposal

  Issues or PRs related to proposals.
• kind/regression

  Categorizes issue or PR as related to a regression from a prior release.
• kind/release-blocking

  Issues or PRs that need to be closed before the next CAPI Operator release
• kind/support

  Categorizes issue or PR as a support question.
• lgtm

  "Looks good to me", 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-kind

  Indicates a PR lacks a `kind/foo` label and requires one.
• needs-ok-to-test

  Indicates a PR that requires an org member to verify it is safe to test.