Skip to content

Route automation proposals through the automation App #9

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
showxu merged 2 commits into from
Oct 5, 2026
Merged

Route automation proposals through the automation App #9

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
542bc79
Require automation proposals to be GitHub-signed commits
showxu Oct 5, 2026
5ed0288
Route automation proposals through the automation App
showxu Oct 5, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 7 additions & 1 deletion MAINTENANCE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -16,7 +16,13 @@ only what they share.
that has no bypass: it blocks deletion and force pushes, requires signed
commits, and accepts only squash-merged pull requests whose required checks
pass. Automation proposes its changes as pull requests that merge
automatically once those checks pass.
automatically once those checks pass. It acts through the Computer MCP
Automation GitHub App, installed only where automation proposes changes: the
App's installation token has GitHub create each proposal commit through the
API, which GitHub signs, and opens the pull request, whose checks then run on
their own. A commit made with `git commit` in a workflow is unsigned, and a
pull request opened with the workflow token waits for manual approval before
its checks run.

## Versions

Expand Down