Skip to content

No labels!

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

58 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.
3
cherry-pick-approved
cherry-pick-approved
Indicates a cherry-pick PR into a release branch has been approved by the release branch manager.
do-not-merge/blocked-paths
do-not-merge/blocked-paths
Indicates that a PR should not merge because it touches files in blocked paths.
do-not-merge/cherry-pick-not-approved
do-not-merge/cherry-pick-not-approved
Indicates that a PR is not yet approved to merge into a release branch.
do-not-merge/hold
do-not-merge/hold
Indicates that a PR should not merge because someone has issued a /hold command.
4
do-not-merge/invalid-commit-message
do-not-merge/invalid-commit-message
Indicates that a PR should not merge because it has an invalid commit message.
do-not-merge/invalid-owners-file
do-not-merge/invalid-owners-file
Indicates that a PR should not merge because it has an invalid OWNERS file in it.
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.
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
good first issue
good first issue
Denotes an issue ready for a new contributor, according to the "help wanted" guidelines.
5
help wanted
help wanted
Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.
8
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/bug
kind/bug
Categorizes issue or PR as related to a bug.
3
kind/ci
kind/ci
Categorizes issue or PR as related to CI or testing.
kind/cleanup
kind/cleanup
Categorizes issue or PR as related to cleaning up code, process, or technical debt.
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.
5
kind/flake
kind/flake
Categorizes issue or PR as related to a flaky test.
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.
6
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 that a PR cannot be merged because it has merge conflicts with HEAD.
2
needs-triage
needs-triage
Indicates an issue 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.
1