Skip to content

No labels!

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

69 labels

Sort
Sort
Alphabetically
Reverse alphabetically
Most issues
Fewest issues
kind/dependency
kind/dependency
Categorizes issue or PR as related to dependency changes.
kind/deprecation
kind/deprecation
Categorizes issue or PR as related to module or feature deprecation.
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/enhancement
kind/enhancement
Categorizes issue or PR as related to enhancement.
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/new-api
kind/new-api
Categorizes issue or PR as related to new api.
kind/regression
kind/regression
Categorizes issue or PR as related to a regression from a prior release.
kind/support
kind/support
Categorizes issue or PR as related to support.
kind/technical-debt
kind/technical-debt
Categorizes issue or PR as related to technical debt.
kind/test
kind/test
Categorizes issue or PR as related to adding a test or fixing a failing test.
kind/upgrade
kind/upgrade
Categorizes issue or PR as related to a module or feature upgrade.
kind/upgrade-test-failure
kind/upgrade-test-failure
Categorizes issue or PR as related to a consistently or frequently failing test.
kind/upstream
kind/upstream
Categorizes issue or PR as related to upstream.
lgtm
lgtm
Indicates that a PR is ready to be merged.
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.
lifecycle/stale
lifecycle/stale
Denotes an issue or PR has remained open with no activity and has become stale.
needs-ok-to-test
needs-ok-to-test
Indicates a PR that requires an org member to verify it is safe to test.
needs-rebase
needs-rebase
Indicates a PR cannot be merged because it has merge conflicts with HEAD.
priority/P0
priority/P0
Highest priority. Must be actively worked on as someone's top priority right now.
priority/P1
priority/P1
Important over the long term, but may not be staffed and/or may need multiple releases to complete.
priority/P2
priority/P2
Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
product/clever
product/clever
Categorizes issue or PR as related to Clever.
product/compass
product/compass
Categorizes issue or PR as related to Compass.
product/need-product
product/need-product
Categorizes issue or PR that needs a product label.
product/oem
product/oem
Categorizes issue or PR as related to oem.
question
question
release-note
release-note
Denotes a PR that will be considered when it comes time to generate release notes.