Skip to content

Labels

Labels

  • approved

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

    Indicates a PR directly modifies the 'pkg/apis' directory
  • area/certificate

    Indicates a PR modifies cert-manager and renewal code
  • area/deploy

    Indicates a PR modifies deployment configuration
  • area/driver

    Indicates a PR modifies CSI driver code
  • area/testing

    Indicates a PR modifies e2e testing code
  • cherry-pick-approved

    Indicates a cherry-pick PR into a release branch has been approved by the release branch manager
  • cybr

    Used by CyberArk-employed maintainers to report to line management what's being worked on.
  • dco-signoff: no

    Indicates that at least one commit in this pull request is missing the DCO sign-off message.
  • dco-signoff: yes

    Indicates that all commits in the pull request have the valid DCO sign-off message.
  • dependencies

    Pull requests that update a dependency file
  • do-not-merge/blocked-paths

    Indicates that a PR should not merge because it touches files in blocked paths.
  • 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-owners-file

  • 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
  • duplicate

    This issue or pull request already exists
  • github_actions

    Pull requests that update GitHub Actions code
  • 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.
  • 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/design

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

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

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

    Categorizes issue or PR as related to a flaky test.