acknowledge-critical-fixes-only

Indicates if the issuer of the label is OK with the policy.

Categorizes an issue or PR as actively needing an API review.

Indicates a PR has been approved by an approver from all required OWNERS files.

area/dependency

Issues or PRs related to dependency changes

Issues or PRs related to Kubernetes licensing

backport-risk-assessed

Indicates a PR to a release branch has been evaluated and considered safe to accept.

backports/unvalidated-commits

Indicates that not all commits come to merged upstream PRs.

backports/validated-commits

Indicates that all commits come to merged upstream PRs.

bugzilla/invalid-bug

Indicates that a referenced Bugzilla bug is invalid for the branch this PR is targeting.

bugzilla/severity-high

Referenced Bugzilla bug's severity is high for the branch this PR is targeting.

bugzilla/severity-low

Referenced Bugzilla bug's severity is low for the branch this PR is targeting.

bugzilla/severity-medium

Referenced Bugzilla bug's severity is medium for the branch this PR is targeting.

bugzilla/severity-unspecified

Referenced Bugzilla bug's severity is unspecified for the PR.

bugzilla/severity-urgent

Referenced Bugzilla bug's severity is urgent for the branch this PR is targeting.

bugzilla/valid-bug

Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting.

cherry-pick-approved

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

dco-signoff: no

Indicates the PR's author has not DCO signed all their commits.

dco-signoff: yes

Indicates the PR's author has DCO signed all their commits.

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

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.

DEPRECATED. Indicates that a PR should not merge. Label can only be manually applied/removed.

good first issue

Denotes an issue ready for a new contributor, according to the "help wanted" guidelines.

Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.

jira/invalid-bug

Indicates that a referenced Jira bug is invalid for the branch this PR is targeting.

jira/severity-critical

Referenced Jira bug's severity is critical for the branch this PR is targeting.

jira/severity-important

Referenced Jira bug's severity is important for the branch this PR is targeting.

jira/severity-informational

Referenced Jira bug's severity is informational for the PR.

jira/severity-low

Referenced Jira bug's severity is low for the branch this PR is targeting.

jira/severity-moderate

Referenced Jira bug's severity is moderate for the branch this PR is targeting.

Indicates that a referenced Jira bug is valid for the branch this PR is targeting.

jira/valid-reference

Indicates that this PR references a valid Jira ticket of any type.

kind/api-change

Categorizes issue or PR as related to adding, removing, or otherwise changing an API

Categorizes issue or PR as related to a bug.

Categorizes issue or PR as related to cleaning up code, process, or technical debt.

kind/dependency-change

Categorizes issue or PR as related to changing dependencies

kind/deprecation

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.

Categorizes issue or PR as related to a new feature.

Categorizes issue or PR as related to a flaky test.

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/rotten

Denotes an issue or PR that has aged beyond stale and will be auto-closed.

lifecycle/stale

Denotes an issue or PR has remained open with no activity and has become stale.

needs-ok-to-test

Indicates a PR that requires an org member to verify it is safe to test.

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

Indicates a non-member PR verified by an org member that is safe to test.

priority/awaiting-more-evidence

Lowest priority. Possibly useful, but not yet enough support to actually get it done.

priority/backlog

Higher priority than priority/awaiting-more-evidence.

priority/critical-urgent

Highest priority. Must be actively worked on as someone's top priority right now.

priority/important-longterm

Important over the long term, but may not be staffed and/or may need multiple releases to complete.

priority/important-soon

Must be staffed and worked on either currently, or very soon, ideally in time for the next release.

release-note-none

Denotes a PR that changes 100-499 lines, ignoring generated files.

Denotes a PR that changes 30-99 lines, ignoring generated files.

Denotes a PR that changes 10-29 lines, ignoring generated files.

Denotes a PR that changes 500-999 lines, ignoring generated files.

Denotes a PR that changes 0-9 lines, ignoring generated files.

Denotes a PR that changes 1000+ lines, ignoring generated files.

staff-eng-approved

Indicates a release branch PR has been approved by a staff engineer (formerly group/pillar lead).

tide/merge-blocker

Denotes an issue that blocks the tide merge queue for a branch while it is open.

tide/merge-method-merge

Denotes a PR that should use a standard merge by tide when it merges.

tide/merge-method-rebase

Denotes a PR that should be rebased by tide when it merges.

tide/merge-method-squash

Denotes a PR that should be squashed by tide when it merges.

triage/duplicate

Indicates an issue is a duplicate of other open issue.

triage/needs-information

Indicates an issue needs more information in order to work on it.

triage/not-reproducible

Indicates an issue can not be reproduced as described.

Indicates an issue that is a support question.

triage/unresolved

Indicates an issue that can not or will not be resolved.

Touching vendor dir or related files

¯\\\_(ツ)_/¯

No labels found. Sorry about that.