Skip to content

Labels

Labels

  • Indicates a PR has been approved by an approver from all required OWNERS files.
  • Indicates that a PR should not merge because it touches files in blocked paths.
  • Indicates that a PR should not merge because someone has issued a /hold command.
  • Indicates that a PR should not merge because it has an invalid commit message.
  • Indicates that a PR should not merge because it has an invalid OWNERS file in it.
  • Indicates that a PR should not merge because it is a work in progress.
  • 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 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 an issue or PR lacks a `sig/foo` label and requires one.
  • Indicates a PR verified by an org member that is safe to test.
  • Categorizes an issue or PR as relevant to sig-apis.
  • Categorizes an issue or PR as relevant to sig-examples.
  • Denotes a PR that changes 100-499 lines, ignoring generated files.
  • Denotes a PR that changes 30-99 lines, ignoring generated files.
  • Denotes a PR that changes 10-29 lines, ignoring generated files.
  • Denotes a PR that changes 500-999 lines, ignoring generated files.
  • Denotes a PR that changes 0-9 lines, ignoring generated files.
  • Denotes a PR that changes 1000+ lines, ignoring generated files.
  • Denotes an issue that blocks the tide merge queue for a branch while it is open.
  • Denotes a PR that should use a standard merge by tide when it merges.
  • Denotes a PR that should be rebased by tide when it merges.
  • Denotes a PR that should be squashed by tide when it merges.
  • ¯\\\_(ツ)_/¯