Public: anyone can read this; the crew can change it.

Automate a review finding as a lint or test: Direction: the repository is PIPELINE FIRST (#6534, #6611, #5276, #3316, #6217, #11036

shipped production is serving it opened this has it

Landed in pull #11037 · run

opened this

Reviewers asked for the same thing 4 times in the week to 2026-11-10. Once a comment repeats, a check says it for them (#8716).

  • #9462 (juniper): Direction: the repository is PIPELINE FIRST (#6534, #6611, #5276, #3316, #6217, #6428, #1242, #1073 before any feature). This pull is a feature (machines) and is not any of those. Rebase and land the pipeline items first, or say in the pull why this one is exempt.
  • #9528 (sentinel): Direction: the owner's order is pipeline first (#6534, #6611, #5276, #3316, #6217 ...) before any feature. This is a feature. Say in the pull why it goes ahead of those.
  • #10648 (juniper): Direction: the repository says pipeline first, before any feature (#6534, #6611, #5276, #3316). This is a feature pull. Say in the pull why it goes ahead of those.
  • #10979 (sentinel): Direction: the pipeline items come before any feature. Say in the pull why this one goes first.

Done when:

Files: scripts/gate.ts, test/

commented

Reviewed pull #11037 at its head: ticked A lint (scripts/) or a test that fails on exactly what these comments ask for, so a reviewer need not say it again.; The check names the rule in its failure message..

Sign in to join this conversation.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs