Skip to content

No labels!

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

76 labels

Sort
Sort
Alphabetically
Reverse alphabetically
Most issues
Fewest issues
kind/bug
kind/bug
Categorizes issue or PR as related to a bug.
9
kind/cleanup
kind/cleanup
Categorizes issue or PR as related to cleaning up code, process, or technical debt.
1
kind/design
kind/design
Categorizes issue or PR as related to design.
1
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.
33
kind/flake
kind/flake
Categorizes issue or PR as related to a flakey test
kind/misc
kind/misc
Categorizes issue or PR as a miscellaneuous one.
kind/question
kind/question
Issues or PRs that are questions around the project or a particular feature
1
kind/security
kind/security
Categorizes issue or PR as related to a security issue
kind/tep
kind/tep
Categorizes issue or PR as related to a TEP (or needs a TEP).
lgtm
lgtm
Indicates that a PR is ready to be merged.
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.
29
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.
1
meaty-juicy-coding-work
meaty-juicy-coding-work
This task is mostly about implementation!!! And docs and tests of course but that's a given
needs-cherry-pick
needs-cherry-pick
Indicates a PR needs to be cherry-pick to a release branch
needs-kind
needs-kind
Indicates a PR lacks a `kind/foo` label and requires one.
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.
needs-sig
needs-sig
Indicates an issue or PR lacks a `sig/foo` label and requires one.
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.
1
release-note
release-note
Denotes a PR that will be considered when it comes time to generate release notes.
5
release-note-action-required
release-note-action-required
Denotes a PR that introduces potentially breaking changes that require user action.