Labels

• lgtm

  Indicates that a PR is ready to be merged.
• lifecycle/active

  Indicates that an issue or PR is actively being worked on by a contributor.
• lifecycle/frozen

  Indicates that an issue or PR should not be auto-closed due to staleness.
• lifecycle/rotten

  Denotes an issue or PR that has aged beyond stale and will be auto-closed.
• lifecycle/stale

  Denotes an issue or PR has remained open with no activity and has become stale.
• midstream/Dockerfile

  A Dockerfile.in sync is needed with midstream
• needs-ok-to-test

  Indicates a PR that requires an org member to verify it is safe to test.
• needs-rebase

  Indicates a PR cannot be merged because it has merge conflicts with HEAD.
• ok-to-test

  Indicates a non-member PR verified by an org member that is safe to test.
• priority/awaiting-more-evidence

  Lowest priority. Possibly useful, but not yet enough support to actually get it done.
• priority/backlog

  Higher priority than priority/awaiting-more-evidence.
• priority/critical-urgent

  Highest priority. Must be actively worked on as someone's top priority right now.
• priority/important-longterm

  Important over the long term, but may not be staffed and/or may need multiple releases to complete.
• priority/important-soon

  Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
• px-approved

  Signifies that Product Support has signed off on this PR
• qe-approved

  Signifies that QE has signed off on this PR
• queue/blocks-others
• queue/critical-fix
• queue/fix
• queue/multiple-rebases
• rebase/manual

  Indicates the PR should not be rebased by the rebasebot.
• release-note

  Denotes a PR that will be considered when it comes time to generate release notes.
• release-note-action-required

  Denotes a PR that introduces potentially breaking changes that require user action.
• release-note-none

  Denotes a PR that doesn't merit a release note.
• release/4.1
• release/4.2
• release/4.3
• release/4.4
• release/4.5
• release/4.6