Epic for Gardener Workload Identity scenarios
API change with impact on API users
Something that is not needed anymore and can be cleaned up
Discussion (engaging others in deciding about multiple options)
Enhancement, improvement, extension
Tracking or fixing a flaky test
Something that impedes developers, operators, users or others in their work
Proof of concept or prototype
Bug that requires deeper analysis after immediate issues were resolved (usually after downtime)
Question (asking for help, advice, or technical detail)
Bug that hit us already in the past and that is reappearing/requires a proper solution
Something that is only solved on the surface, but requires more (re)work to be done properly
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 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 cannot be merged because it has merge conflicts with HEAD.
Indicates a non-member PR verified by an org member that is safe to test.
Related to Garden Linux OS
Related to SUSE Container Host OS
Alicloud platform/infrastructure