Labels

Indicates that a PR should not merge because it has an invalid OWNERS file in it.

Indicates that a PR should not merge because it is a work in progress.

This issue or pull request already exists

Pull requests that update go code

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.

This doesn't seem right

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 CVE.

Categorizes issue or PR as related to a feature/enhancement marked for deprecation.

Categorizes issue or PR as related to a technical design.

Categorizes issue or PR as related to documentation.

Categorizes issue or PR as related to EKS Capability for ACK.

Categorizes issue or PR as related to existing feature enhancements.

Categorizes issue or PR as related to a new feature.

Categorizes issue or PR as related to a new resource.

Categorizes issue or PR as related to a new service.

Categorizes issue or PR as related to a regression from a prior release.

Categorizes issue or PR as a support question.

Categorizes issue or PR as related to a consistently or frequently failing test.

Categorizes issue or PR as related to a flaky test.

Indicates that a PR is ready to be merged.

Indicates that an issue or PR is actively being worked on by a contributor.

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.