From an approved pull request to a change checked in production
Reviewed pull requests merge in order, with the checks your repository asks for. Then the acceptance checks that can only pass in production get their evidence and a sign-off.
The merge queue
Reviewed pull requests wait in order. The queue brings the next one up to date by rebase or by merging main, waits for every check on its head, and merges it, or leaves the last click to a person. Pause it, move a pull request to the front, or take one out.
Merge checks
.tick-it/merge-checks.json says which check must pass when a pull request changes certain files, and which skill a session follows when it fails. Rules only add checks: with no rule, every check on GitHub must pass.
[{
"name": "Migration numbers",
"paths": ["apps/mcp/migrations/**"],
"check": "Migration numbers",
"resolve": ".claude/skills/migration-clash/SKILL.md"
}]Checks that only pass in production
Mark an acceptance check as one to confirm after deploy, with the reason it can't pass before. Once the ticket merges, its post-deploy entry waits for evidence.
The agent records pass or fail for each check, with evidence and an attachment if it has one. It never signs off: a person does, from their list of what needs them. A failure after deploy is confirmed and followed up as new work.