fix: use bot app token in update-flake-sources workflow #57
Conversation
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
PRs created with GITHUB_TOKEN don't trigger CI workflows, which blocked auto-merge on the required "build" status check. Use the org-wide rustledger bot app token instead. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
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
update-flake-sources.ymlusingGITHUB_TOKENdon't trigger CI workflows (GitHub prevents this to avoid infinite loops)buildstatus check never ranBOT_APP_ID/BOT_PRIVATE_KEY) instead, matching the pattern in the rustledger repo'srelease-plz.ymlTest plan
BOT_APP_IDandBOT_PRIVATE_KEYsecrets are available in the rustfava repo (org-wide)🤖 Generated with Claude Code