Skip to content

No labels!

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

88 labels

Sort
Sort
Alphabetically
Reverse alphabetically
Most issues
Fewest issues
4.13-feature
4.13-feature
Indicates the PR's required to go to main before feature freeze of release 4.13
2
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.
8
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.
Bug
Bug
bugzilla/invalid-bug
bugzilla/invalid-bug
Indicates that a referenced Bugzilla bug is invalid for the branch this PR is targeting.
5
bugzilla/severity-high
bugzilla/severity-high
Referenced Bugzilla bug's severity is high for the branch this PR is targeting.
2
bugzilla/severity-low
bugzilla/severity-low
Referenced Bugzilla bug's severity is low for the branch this PR is targeting.
1
bugzilla/severity-medium
bugzilla/severity-medium
Referenced Bugzilla bug's severity is medium for the branch this PR is targeting.
3
bugzilla/severity-unspecified
bugzilla/severity-unspecified
Referenced Bugzilla bug's severity is unspecified for the PR.
2
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.
3
cherry-pick-approved
cherry-pick-approved
Indicates a cherry-pick PR into a release branch has been approved by the release branch manager.
ci
ci
Issues or PRs related to the integration of the ocs-operator repository with openshift-ci
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.
6
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.
8
do-not-merge
do-not-merge
DEPRECATED. Indicates that a PR should not merge. Label can only be manually applied/removed.
docs-approved
docs-approved
Signifies that Docs has signed off on this PR
functest
functest
good first issue
good first issue
Denotes an issue ready for a new contributor, according to the "help wanted" guidelines.
1
help wanted
help wanted
Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.
1
jira/invalid-bug
jira/invalid-bug
Indicates that the referenced jira bug is invalid for the branch this PR is targeting
jira/severity-critical
jira/severity-critical
Referenced Jira bug's severity is critical for the branch this PR is targeting.