Skip to content

No labels!

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

147 labels

Sort
Sort
Alphabetically
Reverse alphabetically
Most issues
Fewest issues
cherry-pick-approved
cherry-pick-approved
Indicates a cherry-pick PR into a release branch has been approved by the release branch manager.
cncf-cla: no
cncf-cla: no
Indicates the PR's author has not signed the CNCF CLA.
2
cncf-cla: yes
cncf-cla: yes
Indicates the PR's author has signed the CNCF CLA.
42
committee/code-of-conduct
committee/code-of-conduct
Denotes an issue or PR intended to be handled by the code of conduct committee.
committee/security-response
committee/security-response
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
do-not-merge/blocked-paths
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
do-not-merge/cherry-pick-not-approved
Indicates that a PR is not yet approved to merge into a release branch.
do-not-merge/contains-merge-commits
do-not-merge/contains-merge-commits
do-not-merge/hold
do-not-merge/hold
Indicates that a PR should not merge because someone has issued a /hold command.
5
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.
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.
9
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.
6
do-not-merge
do-not-merge
DEPRECATED. Indicates that a PR should not merge. Label can only be manually applied/removed.
docker
docker
Pull requests that update Docker code
github_actions
github_actions
Pull requests that update GitHub Actions code
go
go
Pull requests that update Go code
good first issue
good first issue
Denotes an issue ready for a new contributor, according to the "help wanted" guidelines.
8
hacktoberfest-accepted
hacktoberfest-accepted
help wanted
help wanted
Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.
63
kind/api-change
kind/api-change
Categorizes issue or PR as related to adding, removing, or otherwise changing an API
6
kind/backport
kind/backport
Issues or PRs requiring backports
2
kind/bug
kind/bug
Categorizes issue or PR as related to a bug.
73
kind/cleanup
kind/cleanup
Categorizes issue or PR as related to cleaning up code, process, or technical debt.
8
kind/deprecation
kind/deprecation
Categorizes issue or PR as related to a feature/enhancement marked for deprecation.
kind/design
kind/design
Categorizes issue or PR as related to design.
1
kind/documentation
kind/documentation
Categorizes issue or PR as related to documentation.
11
kind/failing-test
kind/failing-test
Categorizes issue or PR as related to a consistently or frequently failing test.
7