Skip to content

No labels!

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

126 labels

Sort
Sort
Alphabetically
Reverse alphabetically
Most issues
Fewest issues
go
go
Pull requests that update Go code
good first issue
good first issue
Denotes an issue ready for a new contributor, according to the "help wanted" guidelines.
help wanted
help wanted
Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.
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/deprecation
kind/deprecation
Categorizes issue or PR as related to a feature/enhancement marked for 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/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.
3
kind/flake
kind/flake
Categorizes issue or PR as related to a flaky test.
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 a support question.
lgtm
lgtm
"Looks good to me", 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.
2
lifecycle/stale
lifecycle/stale
Denotes an issue or PR has remained open with no activity and has become stale.
1
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.
1
needs-sig
needs-sig
Indicates an issue or PR lacks a `sig/foo` label and requires one.
needs-triage
needs-triage
Indicates an issue or PR lacks a `triage/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.
5
performance
performance
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.