Labels
Labels
30 labels
- Indicates that a PR should not merge.
- Indicates a PR cannot be merged because it has merge conflicts with HEAD.
- Indicates that a PR should not merge because it is a work in progress.
- Denotes an issue ready for a new contributor.
- Denotes an issue that needs help from other contributors.
- Categorizes issue or PR as related to a bug (i.e. something is not working).
- Categorizes pull requests that update a dependency file.
- Categorizes issue or PR as related to documentation.
- Categorizes issue or PR as related to a new feature.
- Categorizes issue or PR improving development/releases/Continious Integration (CI).
- Categorizes issue or PR as related to security.
- Categorizes issues related to questions.
- Categorizes issue or PR addressing tests (missing, adding, problem).
- Indicates that a PR is ready to be merged.
- Indicates an issue or PR lacks a `triage/foo` label and requires one.
- Categorizes issues or PRs as high priority.
- Categorizes issues or PRs as low priority.
- Manually request Renovate to recreate/rebase the PR by adding this label.
- Manually request Renovate to stop updating a PR by adding this label.
- Denotes a PR that changes 100-499 lines, ignoring generated files.
- Denotes a PR that changes 30-99 lines, ignoring generated files.
- Denotes a PR that changes 10-29 lines, ignoring generated files.
- Denotes a PR that changes 500-999 lines, ignoring generated files.
- Denotes a PR that changes 0-9 lines, ignoring generated files.
- Denotes a PR that changes 1000+ lines, ignoring generated files.
- Indicates an issue or PR is ready to be actively worked on.
- 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.
- This will not be worked on