Labels
Labels
62 labels
- Affects Kargo's API server
- Affects the Helm chart
- Affects the CI process that runs on PRs and runs following merges to main and release-* branches
- Affects the kargo CLI
- Affects the (main) controller
- Affects custom resource definitions
- Affects developer workflows
- Affects documentation
- Affects the server that responds to webhooks originating from external systems
- Affects the garbage collector
- Affects the server that handles Kargo-specific validations on behalf of the Kubernetes API server
- Affects the controller that manages the Kargo control plane itself
- Affects release automation
- Has security implications and needs to be handled with great caution
- Affects tests (other than unit tests)
- Affects the UI
- Affects how easy or hard it is to use Kargo effectively
- PRs with this label will automatically be back-ported to the release-1.3 branch
- PRs with this label will automatically be back-ported to the release-1.4 branch
- PRs with this label will automatically be back-ported to the release-1.5 branch
- PRs with this label will automatically be back-ported to the release-1.6 branch
- PRs with this label will automatically be back-ported to the release-1.7 branch
- PRs with this label will automatically be back-ported to the release-1.8 branch
- Blocked from progressing further until an issue upstream (i.e. a dependency) has been resolved.
- Pull requests that update a dependency file; mainly used by Dependabot
- Explicitly calls attention to cases where a PR (that might otherwise have been) is NOT backported
- Denotes a PR that a maintainer is explicitly requesting NOT yet be merged by their peers
- Pull requests that update Docker code
- Clarifies that an issue or PR has been closed because of similarity to another
- Pull requests that update GitHub Actions code