Skip to content

No labels!

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

122 labels

Sort
Sort
Alphabetically
Reverse alphabetically
Most issues
Fewest issues
kind/api-change
kind/api-change
Categorizes issue or PR as related to adding, removing, or otherwise changing an API
1
kind/bug
kind/bug
Categorizes issue or PR as related to a bug.
27
kind/cleanup
kind/cleanup
Categorizes issue or PR as related to cleaning up code, process, or technical debt.
20
kind/deprecation
kind/deprecation
Categorizes issue or PR as related to a feature/enhancement marked for deprecation.
1
kind/design
kind/design
Categorizes issue or PR as related to design.
kind/documentation
kind/documentation
Categorizes issue or PR as related to documentation.
7
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.
32
kind/flake
kind/flake
Categorizes issue or PR as related to a flaky test.
2
kind/proposal
kind/proposal
Issues or PRs related to proposals.
1
kind/regression
kind/regression
Categorizes issue or PR as related to a regression from a prior release.
1
kind/support
kind/support
Categorizes issue or PR as a support question.
1
lgtm
lgtm
"Looks good to me", indicates that a PR is ready to be merged.
1
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.
4
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.
4
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.
4
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.
3
ok-to-test
ok-to-test
Indicates a non-member PR verified by an org member that is safe to test.
7
parity
parity
Used to track feature parity with other Azure provisioning tools (AKS, AKS Engine, etc)
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.
15
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.
7
priority/important-soon
priority/important-soon
Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
7
release-note
release-note
Denotes a PR that will be considered when it comes time to generate release notes.
9