Repository navigation
ci: push bot commits with a GitHub App token - #17
Merged
Merged
Conversation
GitHub does not accept GitHub Actions as a ruleset bypass actor, so a GITHUB_TOKEN push cannot get past a "require pull request" rule. Mint a short-lived devicecloud-push-bot token (contents: write only) and push with it; that app is a bypass actor on this repo's rulesets. Falls back to GITHUB_TOKEN while PUSH_APP_ID / PUSH_APP_PRIVATE_KEY are unset. Bot commits now carry the skip-ci marker in their message body: app-token pushes start workflows, GITHUB_TOKEN pushes never did. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
riglar
force-pushed
the
ci/push-app-token
branch
from
October 12, 2026 12:49
acea4c6 to
b7dc744
Compare
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.
Why
The org rulesets now require PRs on protected branches, but this repo was left out: a job here pushes straight to the branch with
GITHUB_TOKEN, and GitHub refuses GitHub Actions as a ruleset bypass actor ("must be part of the ruleset source or owner organization").What changed
contents: writeonly), and pushes with it. That app will be the only bypass actor for bot pushes on this repo.PUSH_APP_ID/PUSH_APP_PRIVATE_KEYare unset it usesGITHUB_TOKEN, as before. Safe to merge first.[skip ci]in its message body. App-token pushes start workflows;GITHUB_TOKENpushes never did. This keeps today's behaviour and avoids loops.After merge
Once the secrets exist, this repo gets added to the "Require pull requests" ruleset with devicecloud-push-bot as a bypass actor.
🤖 Generated with Claude Code