Labels
Labels
24 labels
- Denotes an issue ready for a new contributor.
- Indicates a request for help in order to solve the issue and improve the project
- Categorizes issue or pull request as related to a bug.
- Categorizes issue or pull request as related to cleaning up code, process, or technical debt.
- Categorizes issue or pull request as related to documentation.
- Categorizes issue or pull request as related to enhancement.
- Categorizes issue or pull request as related to a consistently or frequently failing test.
- Categorizes issue or pull request as related to a new feature.
- Indicates a pull request that does not provide any real improvement, thus rejected.
- Denotes a pull request that will be considered when it comes time to generate release notes.
- Denotes a pull request that introduces potentially breaking changes that require user action.
- Denotes a pull request that doesn't merit a release note.
- Lowest priority. Possibly useful, but not yet enough support to actually get it done.
- Higher priority than priority/awaiting-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.
- Indicates an issue is a duplicate of other open issue.
- Indicates an issue needs more information in order to work on it.
- Indicates that a reported issue is not reproducible
- Indicates an issue out of the project's scope.
- Indicates an issue that is a support question.
- Indicates an issue assigned and under investigation.
- Indicates an issue that will not be fixed.