Labels

• ok-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.
• released

  Marks issues as released
• sig/community

  Categorizes an issue or PR as relevant to SIG Community
• sig/community-experience

  Denotes an issue or PR relevant to SIG Community Experience.
• sig/cyborgs

  Categorizes an issue or PR as relevant to SIG Cyborgs and Bots.
• sig/data-science

  Denotes an issue or PR relevant to SIG Data Science.
• sig/devops

  Categorizes an issue or PR as relevant to SIG DevOps.
• sig/docs

  Categorizes an issue or PR as relevant to SIG Docs.
• sig/operations

  Categorizes an issue or PR as relevant to SIG Operations
• sig/pipelines

  Categorizes an issue or PR as relevant to SIG Pipelines (CI/CD)
• sig/services

  Denotes an issue or PR relevant to SIG Services.
• sig/sre

  Categorizes an issue or PR as relevant to SIG SRE
• size/L

  Denotes a PR that changes 100-499 lines, ignoring generated files.
• size/M

  Denotes a PR that changes 30-99 lines, ignoring generated files.
• size/S

  Denotes a PR that changes 10-29 lines, ignoring generated files.
• size/XL

  Denotes a PR that changes 500-999 lines, ignoring generated files.
• size/XS

  Denotes a PR that changes 0-9 lines, ignoring generated files.
• size/XXL

  Denotes a PR that changes 1000+ lines, ignoring generated files.
• tide/merge-blocker

  Denotes an issue that blocks the tide merge queue for a branch while it is open.
• tide/merge-method-merge

  Denotes a PR that should use a standard merge by tide when it merges.
• tide/merge-method-rebase

  Denotes a PR that should be rebased by tide when it merges.
• tide/merge-method-squash

  Denotes a PR that should be squashed by tide when it merges.
• triage/accepted

  Indicates an issue or PR is ready to be actively worked on.
• triage/duplicate

  Indicates an issue is a duplicate of other open issue.
• triage/needs-information

  Indicates an issue needs more information in order to work on it.