This repository was archived by the owner on Nov 27, 2024. It is now read-only.
Labels
Labels
54 labels
- Indicates a PR has been approved by an approver from all required OWNERS files.
- Relates to backend
- Relates to frontend
- Relates to infrastructure
- Relates to metrics
- Relates to reliability
- Relates to security
- Relates to user experience
- Indicates that this is blocked. Link the blocker
- Indicates that a PR should not merge because it touches files in blocked paths.
- Indicates that a PR should not merge because someone has issued a /hold command.
- Indicates that a PR should not merge because it has an invalid commit message.
- Indicates that a PR should not merge because it has an invalid OWNERS file in it.
- Indicates that a PR should not merge because it is a work in progress.
- This issue or pull request already exists
- Good for newcomers
- Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.
- This doesn't seem right
- Categorizes issue or PR as related to a bug.
- Categorizes issue or PR as related to cleaning up code, process, or technical debt.
- Categorizes issue or PR as related to a feature/enhancement marked for deprecation.
- Categorizes issue or PR as related to design.
- Categorizes issue or PR as related to documentation.
- An epic is a large body of work that can be broken down into a number of smaller Issues.
- Categorizes issue or PR as related to a consistently or frequently failing test.
- Categorizes issue or PR as related to a new feature.
- Categorizes issue or PR as related to a flaky test.
- Categorizes issue or PR as related to an incident report.
- Categorizes issue as initiative affecting one or more KRs
- Categorizes issue or PR as related to manual ops work.