-
Notifications
You must be signed in to change notification settings - Fork 21
No labels!
There aren’t any labels for this repository quite yet.
68 labels
kind/failing-test
kind/failing-test
Categorizes issue or PR as related to a consistently or frequently failing test.
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.
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 a PR cannot be merged because it has merge conflicts with HEAD.
priority/awaiting-more-evidence
priority/awaiting-more-evidence
Lowest priority. Possibly useful, but not yet enough support to actually get it done.
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.
priority/important-soon
priority/important-soon
Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
staff-eng-approved
staff-eng-approved
Indicates a release branch PR has been approved by a staff engineer (formerly group/pillar lead).
tide/merge-blocker
tide/merge-blocker
Denotes an issue that blocks the tide merge queue for a branch while it is open.
tide/merge-method-merge
tide/merge-method-merge
Denotes a PR that should use a standard merge by tide when it merges.
tide/merge-method-rebase
tide/merge-method-rebase
Denotes a PR that should be rebased by tide when it merges.