Many repositories
llms.txtlists every page for an agent
Who it is for
Your stacks span many repositories, and one team sets the approvers for all of them.
Features
- A control repo holds the approvers and the engine pins
- Each repository gets its settings as a pull request, so a change to them is reviewed like any other
Every setup gets
- One preview note on every pull request
- Updates of the previews you approved
- No overlapping or stale updates
- Re-preview from a comment
- Scheduled drift checks
- Separate identities to preview and to update
- Policy on every preview, CrossGuard included
- An audit trail in your own repository
- Secrets stay [secret] in notes
- Your backend and your runners, as they are
First step
Then read
- How-to
- Write a policyApprovals runbook
- Explanation
- The control repo
- Reference
- Configuration