Skip to content

No labels!

There aren’t any labels for this repository quite yet.

44 labels

Sort
Sort
Alphabetically
Reverse alphabetically
Most issues
Fewest issues
approved
approved
Indicates a PR has been approved by an approver from all required OWNERS files.
blog
blog
New blog post
cncf-cla: no
cncf-cla: no
Indicates the PR's author has not signed the CNCF CLA.
cncf-cla: yes
cncf-cla: yes
Indicates the PR's author has signed the CNCF CLA.
committee/conduct
committee/conduct
Denotes an issue or PR intended to be handled by the code of conduct committee.
committee/product-security
committee/product-security
Denotes an issue or PR intended to be handled by the product security committee.
committee/steering
committee/steering
Denotes an issue or PR intended to be handled by the steering committee.
dependencies
dependencies
Pull requests that update a dependency file
2
do-not-merge/hold
do-not-merge/hold
Indicates that a PR should not merge because someone has issued a /hold command.
1
do-not-merge/invalid-commit-message
do-not-merge/invalid-commit-message
Indicates that a PR should not merge because it has an invalid commit message.
1
do-not-merge/invalid-owners-file
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
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
do-not-merge/work-in-progress
Indicates that a PR should not merge because it is a work in progress.
1
good first issue
good first issue
Denotes an issue ready for a new contributor, according to the "help wanted" guidelines.
2
help wanted
help wanted
Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.
10
kind/api-change
kind/api-change
Categorizes issue or PR as related to adding, removing, or otherwise changing an API
kind/bug
kind/bug
Categorizes issue or PR as related to a bug.
kind/cleanup
kind/cleanup
Categorizes issue or PR as related to cleaning up code, process, or technical debt.
kind/design
kind/design
Categorizes issue or PR as related to design.
kind/documentation
kind/documentation
Categorizes issue or PR as related to documentation.
6
kind/failing-test
kind/failing-test
Categorizes issue or PR as related to a consistently or frequently failing test.
kind/feature
kind/feature
Categorizes issue or PR as related to a new feature.
kind/question
kind/question
Indicates an issue that is a support question.
lgtm
lgtm
Indicates that a PR is ready to be merged.
9
lifecycle/active
lifecycle/active
Indicates that an issue or PR is actively being worked on by a contributor.
lifecycle/frozen
lifecycle/frozen
Indicates that an issue or PR should not be auto-closed due to staleness.
5
lifecycle/stale
lifecycle/stale
13
needs-rebase
needs-rebase
Indicates a PR cannot be merged because it has merge conflicts with HEAD.
20
new-feature
new-feature
priority/awaiting-more-evidence
priority/awaiting-more-evidence
Lowest priority. Possibly useful, but not yet enough support to actually get it done.