Labels
Labels
28 labels
- Denotes a PR that introduces potentially breaking changes that require user action.
- Pull requests that update a dependency file
- Signal to Mergify to block merging of the PR.
- Pull requests that update GitHub Actions code
- Denotes an issue ready for a new contributor, according to the "help wanted" guidelines.
- Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.
- 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 design.
- Categorizes issue or PR as related to documentation.
- 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 organization and governance.
- Categorizes issue or PR as related to a regression from a prior release.
- Categorizes issue or PR as a support question.
- Lowest priority. Possibly useful, but not yet enough support to actually get it done.
- Higher priority than priority/awaiting-more-evidence.
- Highest priority. Must be actively worked on as someone's top priority right now.
- Important over the long term, but may not be staffed and/or may need multiple releases to complete.
- Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
- Signal to Mergify to merge the PR.
- Items that appear on the roadmap. Implies priority/important-soon or priority/important-longterm.
- Indicates a PR or issue that requires discussion
- Indicates an issue is a duplicate of other open issue.
- Indicates an issue needs more information in order to work on it.
- Indicates an issue can not be reproduced as described.
- Indicates an issue that can not or will not be resolved.