Skip to content

No labels!

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

68 labels

Sort
Sort
Alphabetically
Reverse alphabetically
Most issues
Fewest issues
api-review
api-review
Categorizes an issue or PR as actively needing an API review.
approved
approved
Indicates a PR has been approved by an approver from all required OWNERS files.
2
area/dependency
area/dependency
Issues or PRs related to dependency changes
area/licensing
area/licensing
Issues or PRs related to Kubernetes licensing
backports/unvalidated-commits
backports/unvalidated-commits
Indicates that not all commits come to merged upstream PRs.
backports/validated-commits
backports/validated-commits
Indicates that all commits come to merged upstream PRs.
bugzilla/invalid-bug
bugzilla/invalid-bug
Indicates that a referenced Bugzilla bug is invalid for the branch this PR is targeting.
bugzilla/severity-high
bugzilla/severity-high
Referenced Bugzilla bug's severity is high for the branch this PR is targeting.
bugzilla/severity-low
bugzilla/severity-low
Referenced Bugzilla bug's severity is low for the branch this PR is targeting.
bugzilla/severity-medium
bugzilla/severity-medium
Referenced Bugzilla bug's severity is medium for the branch this PR is targeting.
bugzilla/severity-unspecified
bugzilla/severity-unspecified
Referenced Bugzilla bug's severity is unspecified for the PR.
bugzilla/severity-urgent
bugzilla/severity-urgent
Referenced Bugzilla bug's severity is urgent for the branch this PR is targeting.
bugzilla/valid-bug
bugzilla/valid-bug
Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting.
cherry-pick-approved
cherry-pick-approved
Indicates a cherry-pick PR into a release branch has been approved by the release branch manager.
dco-signoff: no
dco-signoff: no
Indicates the PR's author has not DCO signed all their commits.
dco-signoff: yes
dco-signoff: yes
Indicates the PR's author has DCO signed all their commits.
3
dependencies
dependencies
Pull requests that update a dependency file
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/hold
do-not-merge/hold
Indicates that a PR should not merge because someone has issued a /hold command.
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.
2
do-not-merge
do-not-merge
DEPRECATED. Indicates that a PR should not merge. Label can only be manually applied/removed.
documentation
documentation
Improvements or additions to documentation
good first issue
good first issue
Denotes an issue ready for a new contributor, according to the "help wanted" guidelines.
help wanted
help wanted
Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.
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/dependency-change
kind/dependency-change
Categorizes issue or PR as related to changing dependencies