Skip to content

No labels!

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

50 labels

Sort
Sort
Alphabetically
Reverse alphabetically
Most issues
Fewest issues
approved
approved
Indicates a PR has been approved by an approver from all required OWNERS files.
bug
bug
Something isn't working
dco-signoff: no
dco-signoff: no
Indicates the PR's author has not DCO signed all their commits.
2
dco-signoff: yes
dco-signoff: yes
Indicates the PR's author has DCO signed all their commits.
4
dependencies
dependencies
Pull requests that update a dependency file
do-not-merge/hold
do-not-merge/hold
Indicates that a PR should not merge because someone has issued a /hold command.
do-not-merge/invalid-owners-file
do-not-merge/invalid-owners-file
do-not-merge/release-note-label-needed
do-not-merge/release-note-label-needed
Indicates that a PR should not merge because it's missing one of the release note labels.
2
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.
1
duplicate
duplicate
This issue or pull request already exists
enhancement
enhancement
New feature or request
good first issue
good first issue
Good for newcomers
help wanted
help wanted
Extra attention is needed
invalid
invalid
This doesn't seem right
kind/api-change
kind/api-change
Categorizes issue or PR as related to adding, removing, or otherwise changing an API
kind/blocker
kind/blocker
kind/bug
kind/bug
kind/enhancement
kind/enhancement
kind/proposal
kind/proposal
kind/question
kind/question
kind/tracker
kind/tracker
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.
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.
needs-ok-to-test
needs-ok-to-test
Indicates a PR that requires an org member to verify it is safe to test.
3
needs-rebase
needs-rebase
Indicates a PR cannot be merged because it has merge conflicts with HEAD.
2
ok-to-test
ok-to-test
Indicates a non-member PR verified by an org member that is safe to test.
question
question
Further information is requested