Labels

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)

Outage that requires root cause analysis after issues were mitigated (usually after downtime)

Bug that hit us already in the past and that is reappearing/requires a proper solution

Roadmap BLI

General task

Something that is only solved on the surface, but requires more (re)work to be done properly

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.

Temporarily on hold (will not age; may have dependencies, lack priority, miss feedback, etc.)

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.

Should not be merged via 'Squash and merge' to keep separate commits

Should be merged via 'Squash and merge'

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.

Needs (more) changes

Needs to be cherry-picked to older version

Needs (more) documentation

Needs help by someone else

Needs to keep the issue open, no auto close

Needs approval for merging

Needs approval for testing (check PR in detail before setting this label because PR is run on CI/CD)

Needs git rebase

Needs (proper) release notes