How work reaches main

Why every change to a repository lands the same way, and who does which step.

Every change lands the same way, whatever the service's maturity (law feature-branch-per-ticket):

  1. Every change starts from a Sparrow task.
  2. The work is one commit on a branch named feat-<ticket>-<short-description>, such as feat-spr-9-user-docs.
  3. The agent pushes that branch, opens its pull request and moves the task to Reviewing. If your review asks for changes, the agent amends the one commit and pushes it again.
  4. You review the pull request and land it with "Rebase and merge". When you turned the task's reviewRequiresValidation off, the repository's landing automation lands it instead, once every check passes.
  5. In a repository with landing automation, that automation moves the task. Whoever merged the pull request, once every workflow run on the merged commit has succeeded it moves the task to Completed, and when one didn't succeed (it failed, was cancelled or timed out) it moves the task to Blocked. If a re-run of that run later succeeds, it moves the task from Blocked to Completed. You can still move any task yourself, and your move stands. Without that automation, you move the task to Completed after the merge.

Agents never land pull requests, and never move a merged task to Completed or Blocked where the landing automation exists. Where it doesn't, they move a task to Completed only where you granted that in writing for the task or batch, after the merge and every post-merge workflow succeeded (laws feature-branch-per-ticket 5.0.0 and ticket-batches-land-one-pull-request-at-a-time 3.0.0; Sparrow ADR-0026 and passerines ADR-0010 give the reasons). They never push to main: when something must reach main directly, they hand you the command (law agents-never-git-push-to-main).