[ci] Use BOT_TOKEN for the Flex endpoint push and PR diff comment#1539
Merged
Conversation
The default GITHUB_TOKEN is now read-only, so pushing the generated Flex endpoint and posting the recipe-diff comment failed (403 / "Resource not accessible by integration"). Authenticate both via the BOT_TOKEN without persisting it into the checkout credentials. Co-Authored-By: Claude Opus 4.8 (1M context) <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
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.
The QA workflow currently fails on every PR at two steps:
git push origin -f flex/pull-Nreturns403(exit code 128)Resource not accessible by integrationBoth steps relied on the default
GITHUB_TOKENpersisted byactions/checkout. Since that token was reduced to read-only, neither the push nor the PR comment can succeed. The steps that were already migrated toBOT_TOKEN(secrets.token) — Automerge, MIT lint — keep working.This authenticates both steps via
BOT_TOKEN:https://x-access-token:<token>@github.com/<repo>URL, so the write token is not persisted into the checkout credentials and is never exposed to the untrustedpull_request_targetmerge ref.GITHUB_TOKENenv var.🤖 Generated with Claude Code