Labels
Labels
104 labels
- Indicates that a PR should not merge because it's missing one of the release note labels.
- Indicates that a PR should not merge because it is a work in progress.
- Signifies that Docs has signed off on this PR
- Improvements or additions to documentation
- Required for GA release
- 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.
- Indicates that a referenced Jira bug is invalid for the branch this PR is targeting.
- Referenced Jira bug's severity is critical for the branch this PR is targeting.
- Referenced Jira bug's severity is important for the branch this PR is targeting.
- Referenced Jira bug's severity is informational for the PR.
- Referenced Jira bug's severity is low for the branch this PR is targeting.
- Referenced Jira bug's severity is moderate for the branch this PR is targeting.
- Indicates that the referenced Jira bug does not require a dependent bug.
- Indicates that a referenced Jira bug is valid for the branch this PR is targeting.
- Indicates that this PR references a valid Jira ticket of any type.
- Categorizes issue or PR as related to adding, removing, or otherwise changing an API
- 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 changing dependencies
- 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 a flaky test.
- Prioritize Konflux PR review