Labels
Labels
169 labels
- Indicates that an issue or PR should not be auto-closed due to staleness.
- Denotes an issue or PR that has aged beyond stale and will be auto-closed.
- Denotes an issue or PR has remained open with no activity and has become stale.
- Indicates an issue needs some investigation.
- Indicates a PR lacks a `kind/foo` label and requires one.
- Indicates a PR that requires an org member to verify it is safe to test.
- Indicates a PR lacks a `priority/foo` label and requires one.
- Indicates a PR cannot be merged because it has merge conflicts with HEAD.
- Indicates an issue or PR lacks a `triage/foo` label and requires one.
- Indicates a non-member PR verified by an org member that is safe to test.
- Operator Lifecycle Manager
- 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.
- Infra and communication stuff
- PRs related to prow auto generation automation
- Issues related to prow olm automation
- Pull requests that update Python code
- Clarification questions
- AWS RAM integration issues
- Indicates issues or PRs that are related to acm-controller.
- Indicates issues or PRs that are related to acmpca-controller.
- Indicates issues or PRs related to all the service controllers.
- Indicates issues or PRs that are related to apigateway-controller.
- Indicates issues or PRs that are related to apigatewayv2-controller.
- Indicates issues or PRs that are related to applicationautoscaling-controller.
- Indicates issues or PRs that are related to athena-controller.