Skip to content

No labels!

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

85 labels

Sort
Sort
Alphabetically
Reverse alphabetically
Most issues
Fewest issues
jira/valid-bug
jira/valid-bug
Indicates that the referenced jira bug is valid for the branch this PR is targeting
jira/valid-reference
jira/valid-reference
Indicates that this PR references a valid jira ticket of any type
kind/api-change
kind/api-change
Categorizes issue or PR as related to adding, removing, or otherwise changing an API
kind/bug
kind/bug
Categorizes issue or PR as related to a bug.
kind/cleanup
kind/cleanup
Categorizes issue or PR as related to cleaning up code, process, or technical debt.
kind/dependency-change
kind/dependency-change
Categorizes issue or PR as related to changing dependencies
kind/design
kind/design
Categorizes issue or PR as related to design.
kind/documentation
kind/documentation
Categorizes issue or PR as related to documentation.
kind/failing-test
kind/failing-test
Categorizes issue or PR as related to a consistently or frequently failing test.
kind/feature
kind/feature
Categorizes issue or PR as related to a new feature.
kind/flake
kind/flake
Categorizes issue or PR as related to a flaky test.
kind/test-flake
kind/test-flake
Categorizes issue or PR as related to test flakes.
lgtm
lgtm
Indicates that a PR is ready to be merged.
2
lifecycle/active
lifecycle/active
Indicates that an issue or PR is actively being worked on by a contributor.
lifecycle/frozen
lifecycle/frozen
Indicates that an issue or PR should not be auto-closed due to staleness.
lifecycle/rotten
lifecycle/rotten
Denotes an issue or PR that has aged beyond stale and will be auto-closed.
1
lifecycle/stale
lifecycle/stale
Denotes an issue or PR has remained open with no activity and has become stale.
mvp
mvp
Required for the next minimum viable product.
needs-ok-to-test
needs-ok-to-test
Indicates a PR that requires an org member to verify it is safe to test.
7
needs-rebase
needs-rebase
Indicates a PR cannot be merged because it has merge conflicts with HEAD.
25
ocs to ocs
ocs to ocs
ok-to-test
ok-to-test
Indicates a non-member PR verified by an org member that is safe to test.
3
priority/awaiting-more-evidence
priority/awaiting-more-evidence
Lowest priority. Possibly useful, but not yet enough support to actually get it done.
priority/backlog
priority/backlog
Higher priority than priority/awaiting-more-evidence.
priority/critical-urgent
priority/critical-urgent
Highest priority. Must be actively worked on as someone's top priority right now.
priority/important-longterm
priority/important-longterm
Important over the long term, but may not be staffed and/or may need multiple releases to complete.
priority/important-soon
priority/important-soon
Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
priority/0-critical
priority/0-critical
Highest priority. Must be actively worked on as someone's top priority right now.
priority/1-high
priority/1-high
priority/2-medium
priority/2-medium