Labels
Labels
57 labels
- Categorizes issues as operational alert
- Indicates a PR has been approved by an approver from all required OWNERS files.
- This Issue or PR is being worked on by a bot
- Pull requests that update a dependency file
- 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 OWNERS file in it.
- Indicates that a PR should not merge because it is a work in progress.
- Improvements or additions to documentation
- Pull requests that update GitHub Actions code
- Denotes an issue ready for a new contributor, according to the "help wanted" guidelines.
- Issues targeting the hacktoberfest participants.
- PR that has been accepted for hacktoberfest!
- Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.
- Categorizes issues as operational alert
- Categorizes issue or PR as related to a bug.
- Categorizes issue or PR as related to cleaning up code, process, or technical debt.
- This is an Issue or PR someone want to give a demo or request a demo.
- Categorizes issue or PR as related to a feature/enhancement marked for deprecation.
- Categorizes issue or PR as related to documentation.
- Categorizes issue or PR as related to a new feature.
- Categorizes issue or PR as a support question.
- Indicates that a PR is ready to be merged.
- Indicates that an issue or PR is actively being worked on by a contributor.
- Indicates that an issue or PR should not be auto-closed due to staleness.
- Denotes an issue or PR that has aged beyond stale and will be auto-closed.
- Denotes an issue or PR has remained open with no activity and has become stale.
- Indicates a PR that requires an org member to verify it is safe to test.