Skip to content

No labels!

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

121 labels

Sort
Sort
Alphabetically
Reverse alphabetically
Most issues
Fewest issues
lifecycle/frozen
lifecycle/frozen
Indicates that an issue or PR should not be auto-closed due to staleness.
40
cncf-cla: yes
cncf-cla: yes
Indicates the PR's author has signed the CNCF CLA.
28
kind/feature
kind/feature
Categorizes issue or PR as related to a new feature.
19
help wanted
help wanted
Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.
19
kind/support
kind/support
Categorizes issue or PR as a support question.
18
ok-to-test
ok-to-test
Indicates a non-member PR verified by an org member that is safe to test.
14
do-not-merge/hold
do-not-merge/hold
Indicates that a PR should not merge because someone has issued a /hold command.
11
priority/important-longterm
priority/important-longterm
Important over the long term, but may not be staffed and/or may need multiple releases to complete.
10
lifecycle/stale
lifecycle/stale
Denotes an issue or PR has remained open with no activity and has become stale.
10
size/S
size/S
Denotes a PR that changes 10-29 lines, ignoring generated files.
8
priority/backlog
priority/backlog
Higher priority than priority/awaiting-more-evidence.
8
kind/design
kind/design
Categorizes issue or PR as related to design.
8
size/XXL
size/XXL
Denotes a PR that changes 1000+ lines, ignoring generated files.
7
size/M
size/M
Denotes a PR that changes 30-99 lines, ignoring generated files.
7
lifecycle/rotten
lifecycle/rotten
Denotes an issue or PR that has aged beyond stale and will be auto-closed.
6
kind/bug
kind/bug
Categorizes issue or PR as related to a bug.
5
size/L
size/L
Denotes a PR that changes 100-499 lines, ignoring generated files.
4
tide/merge-method-squash
tide/merge-method-squash
Denotes a PR that should be squashed by tide when it merges.
3
priority/important-soon
priority/important-soon
Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
3
needs-rebase
needs-rebase
Indicates a PR cannot be merged because it has merge conflicts with HEAD.
3
needs-ok-to-test
needs-ok-to-test
Indicates a PR that requires an org member to verify it is safe to test.
3
kind/documentation
kind/documentation
Categorizes issue or PR as related to documentation.
3
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.
3
priority/awaiting-more-evidence
priority/awaiting-more-evidence
Lowest priority. Possibly useful, but not yet enough support to actually get it done.
2
lgtm
lgtm
"Looks good to me", indicates that a PR is ready to be merged.
2
approved
approved
Indicates a PR has been approved by an approver from all required OWNERS files.
2
wg/api-expression
wg/api-expression
Categorizes an issue or PR as relevant to WG API Expression.
1
triage/accepted
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
1
size/XS
size/XS
Denotes a PR that changes 0-9 lines, ignoring generated files.
1
size/XL
size/XL
Denotes a PR that changes 500-999 lines, ignoring generated files.
1