Gating and merging AI agent code
AI coding
Gating and merging AI agent code
- A Pre-Merge Checklist for Agent-Generated Code
- A Two-Step Apply for Agent Writes: Dry Run, Then Commit
- Branch Protection Rules for Agent Commits: What to Require
- Branch Protection Rules That Assume the Author Is a Bot
- Irreversible Actions an Agent Must Never Take Without a Human
- Scoping the Gate to Changed Lines: Coverage and Mutation
- Approval Gates for Agent Commits: What a Human Must Sign Off On
- Binding a Required Check to a Commit Hash and a Signing Key
- Code Owners for Agent Branches: A Rules Table
- Diff Budget Enforcement: Automating the Limits You Set
- Fail-Closed Gates: When the Tamper Detector Errors
- Mapping Diff Lines to Executed Code
- Pinning a Required Check to One Commit
- Rerunning Your Gates When a Model Version Changes
- Reviewing an Agent's Commit History: Squash, Rebase or Leave It
- Scheduled Full Runs vs. Diff-Scoped Gates
- What a Merge Gate Should Log for an Agent Branch
- What a Merge Queue Costs in CI Minutes and How to Budget It
- When a Check Should Fail Closed: Errors, Timeouts and Refusals