Skip to content

No labels!

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

87 labels

Sort
Sort
Alphabetically
Reverse alphabetically
Most issues
Fewest issues
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.
5
Epic
Epic
Issues that should be considered as Epics (aka multiple sub-tasks, …)
4
good first issue
good first issue
Denotes an issue ready for a new contributor, according to the "help wanted" guidelines.
14
Hacktoberfest
Hacktoberfest
Categorizes issue as one for Hacktoberfest 2021
4
hacktoberfest-accepted
hacktoberfest-accepted
Categorizes PRs as one accepted Hacktoberfest 2021
help wanted
help wanted
Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.
42
kind/api-change
kind/api-change
Categorizes issue or PR as related to adding, removing, or otherwise changing an API
kind/beta-blocking
kind/beta-blocking
Categorizes issue or PR as related to the beta api
kind/bug
kind/bug
Categorizes issue or PR as related to a bug.
107
kind/cleanup
kind/cleanup
Categorizes issue or PR as related to cleaning up code, process, or technical debt.
14
kind/design
kind/design
Categorizes issue or PR as related to design.
3
kind/documentation
kind/documentation
Categorizes issue or PR as related to documentation.
18
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.
166
kind/flake
kind/flake
Categorizes issue or PR as related to a flakey test
5
kind/misc
kind/misc
Categorizes issue or PR as a miscellaneuous one.
25
kind/question
kind/question
Issues or PRs that are questions around the project or a particular feature
11
kind/security
kind/security
Categorizes issue or PR as related to a security issue
3
kind/tep
kind/tep
Categorizes issue or PR as related to a TEP (or needs a TEP).
1
lgtm
lgtm
Indicates that a PR is ready to be merged.
3
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.
121
lifecycle/rotten
lifecycle/rotten
Denotes an issue or PR that has aged beyond stale and will be auto-closed.
9
lifecycle/stale
lifecycle/stale
Denotes an issue or PR has remained open with no activity and has become stale.
10
maybe-next-milestone
maybe-next-milestone
For consideration when planning the next milestone
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
1
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.
4
needs-rebase
needs-rebase
Indicates a PR cannot be merged because it has merge conflicts with HEAD.
15