Labels

Further information is requested

Categorizes issue or PR as related to test flakes.

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.

A Dockerfile.in sync is needed with midstream

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.

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.

Signifies that Product Support has signed off on this PR

Signifies that QE has signed off on this PR

Indicates a PR has been reviewed by automated tools and is ready for human review

Indicates the PR should not be rebased by the rebasebot.

Denotes a PR that will be considered when it comes time to generate release notes.

Denotes a PR that introduces potentially breaking changes that require user action.

Denotes a PR that doesn't merit a release note.