Skip to content

Labels

Labels

  • activity

    event that would be ended in certain deadlines
  • approved

    Indicates a PR has been approved by an approver from all required OWNERS files.
  • cncf-cla: no

    Indicates the PR's author has not signed the CNCF CLA.
  • cncf-cla: yes

    Indicates the PR's author has signed the CNCF CLA.
  • committee/conduct

    Denotes an issue or PR intended to be handled by the code of conduct committee.
  • committee/product-security

    Denotes an issue or PR intended to be handled by the product security committee.
  • committee/steering

    Denotes an issue or PR intended to be handled by the steering committee.
  • 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.
  • duplicate

    This issue or pull request already exists
  • 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/answered question

    questions that has been answered, for reference
  • 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/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/question

    Indicates an issue that is 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/past activity

    Past activities for future reference, not valid any more
  • needs-rebase

    Indicates a PR cannot be merged because it has merge conflicts with HEAD.