CI/CD integration
Route here when search intent is GitHub Actions, GitLab CI, or scheduled automation — implementation detail lives in Automation.
Minimal CI pattern
Section titled “Minimal CI pattern”bmo run --quiet --auto-approve-tools "Fix the failing test in pkg/foo"Warning: --auto-approve-tools skips permission prompts. Pair with
Sandbox (docker or ssh) when CI runs on shared
runners.
Safer CI patterns
Section titled “Safer CI patterns”| Pattern | Tradeoff |
|---|---|
| Read-only analysis | Disable write tools via config |
| Proposal-only | Agent queues patch; human merges |
| Recipe | bmo recipe run for repeatable jobs |
| Scheduled | options.automation.jobs cron entries |
Auth in CI
Section titled “Auth in CI”- Inject provider keys via CI secrets — never commit keys.
- See Authentication.
Observability
Section titled “Observability”Capture logs and exit codes from bmo run. For post-hoc timeline, archive
the BMO data dir artifact or use session IDs in logs. See
Run observability.
Related
Section titled “Related”- Cost and operations
- Security and data
- Proof gallery — headless capture