-
-
Notifications
You must be signed in to change notification settings - Fork 1
No labels!
There aren’t any labels for this repository quite yet.
28 labels
backport-risk-assessed
backport-risk-assessed
Indicates a PR to a release branch has been evaluated and considered safe to accept.
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-urgent
bugzilla/severity-urgent
Referenced Bugzilla bug's severity is urgent for the branch this PR is targeting.
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.
good first issue
good first issue
Denotes an issue ready for a new contributor, according to the "help wanted" guidelines.
jira/invalid-bug
jira/invalid-bug
Indicates that a 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.
jira/severity-important
jira/severity-important
Referenced Jira bug's severity is important for the branch this PR is targeting.
jira/valid-bug
jira/valid-bug
Indicates that a referenced Jira bug is valid for the branch this PR is targeting.
kind/api-change
kind/api-change
Categorizes issue or PR as related to adding, removing, or otherwise changing an API
kind/dependency-change
kind/dependency-change
Categorizes issue or PR as related to changing dependencies
lifecycle/active
lifecycle/active
Indicates that an issue or PR is actively being worked on by a contributor.
needs-ok-to-test
needs-ok-to-test
Indicates a PR that requires an org member to verify it is safe to test.
priority/critical-urgent
priority/critical-urgent
Highest priority. Must be actively worked on as someone's top priority right now.
tide/merge-method-rebase
tide/merge-method-rebase
Denotes a PR that should be rebased by tide when it merges.