Skip to content

No labels!

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

189 labels

Sort
Sort
Alphabetically
Reverse alphabetically
Most issues
Fewest issues
area/prow/pod-utilities
area/prow/pod-utilities
Issues or PRs related to prow's pod-utilities component
2
area/prow/pubsub
area/prow/pubsub
Issues or PRs related to prow's pubsub reporter component
area/prow/sidecar
area/prow/sidecar
Issues or PRs related to prow's sidecar component
area/prow/sinker
area/prow/sinker
Issues or PRs related to prow's sinker component
area/prow/splice
area/prow/splice
Issues or PRs related to prow's splice component
area/prow/spyglass
area/prow/spyglass
Issues or PRs related to prow's spyglass UI
area/prow/status-reconciler
area/prow/status-reconciler
Issues or PRs related to reconciling status when jobs change
area/prow/tide
area/prow/tide
Issues or PRs related to prow's tide component
1
area/prow/tot
area/prow/tot
Issues or PRs related to prow's tot component
area/prow
area/prow
Issues or PRs related to prow
11
area/release-eng
area/release-eng
Issues or PRs related to the Release Engineering subproject
8
area/robots
area/robots
Issues or PRs related to code in /robots
1
area/scenarios
area/scenarios
area/so-crazy-it-just-might-work
area/so-crazy-it-just-might-work
area/testgrid
area/testgrid
4
area/triage
area/triage
area/velodrome
area/velodrome
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.
cncf-cla: yes
cncf-cla: yes
Indicates the PR's author has signed the CNCF CLA.
55
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/hold
do-not-merge/hold
Indicates that a PR should not merge because someone has issued a /hold command.
18
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.
1
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.