-
Notifications
You must be signed in to change notification settings - Fork 4
No labels!
There aren’t any labels for this repository quite yet.
206 labels
area/workload-api/cronjob
area/workload-api/cronjob
Issues or PRs related to workload API's cronjob features
area/workload-api/daemonset
area/workload-api/daemonset
Issues or PRs related to workload API's daemonset features
area/workload-api/deployment
area/workload-api/deployment
Issues or PRs related to workload API's deployment features
cherry-pick-approved
cherry-pick-approved
Indicates a cherry-pick PR into a release branch has been approved by the release branch manager.
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.
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
Indicates a PR which 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.
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.