Open catalog proposals with the automation App - #35
Merged
Merged
Conversation
GitHub now holds pull_request runs on pull requests opened with the job token until someone approves them, and checks from the dispatched Website CI run never satisfy the required checks, so a catalog proposal could not merge on its own. When the catalog changes, the Pages job now mints a Contents and Pull requests installation token from the organization's Computer MCP Automation App and uses it to create the signed proposal and its pull request, whose Website CI then runs on its own. The job token becomes read-only and the dispatch step is removed.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Since June 2026 GitHub holds
pull_requestruns on pull requests opened with the job token until someone with write access approves them, and checks from the dispatchedci.ymlrun never satisfy a ruleset's required checks (computer-mcp/homebrew-tap#6 waited on exactly this). A catalog proposal therefore could not merge on its own.When the generated catalog differs from
master, the Pages job now mints an installation token from the organization's Computer MCP Automation GitHub App (Contents and Pull requests write, installed only on this repository and the tap) and uses it to create the signed proposal and its pull request, so Website CI runs on the pull request and auto-merge completes. An unchanged catalog mints no token, so App trouble cannot block ordinary deployments. The job token becomes read-only and the dispatch step is removed. Docs describe the App and itsAUTOMATION_APP_CLIENT_IDvariable andAUTOMATION_APP_PRIVATE_KEYsecret.Merge after the App is installed and its credentials are configured.