Use GitHub App token for release workflow CI triggers#15
Merged
Conversation
Events created by GITHUB_TOKEN are intentionally suppressed by GitHub to prevent infinite loops, which means CI never triggers on bot-created release PRs. Switch to a GitHub App token for both git push and PR creation so that pull_request events (opened/synchronize) fire and trigger CI workflows. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
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
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.
Summary
actions/create-github-app-token@v1) instead ofGITHUB_TOKENfor git push and PR creation in therelease-version-syncworkflowGITHUB_TOKENto prevent infinite loopspush(triggerspull_request: synchronize) andgh pr create(triggerspull_request: opened) now use the App token so CI runs in all casesTest plan
release/0.0.5) and verify the Release Version Sync workflow runs🤖 Generated with Claude Code