fix(framework): authenticate the Actions run-branch push explicitly (#1085) - #1088
Merged
Conversation
The Push the run branch step (#1085) used a plain `git push origin`, which relies on the checkout's persisted credentials. The claude-code-action step runs its own git setup and leaves those unusable, so the push failed with "Authentication failed for github.com". Push through an x-access-token URL built from the workflow token instead. Refs #1085 #1087
suleimansh
added
bug
suleimansh
marked this pull request as ready for review
July 23, 2026 19:06
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.
Follow-up to #1087. Live-testing the two-turn Actions flow showed the run's agent commits fine, but the new "Push the run branch" step failed:
The step used a plain
git push origin, which relies on the credentialsactions/checkoutpersists. Theclaude-code-actionstep runs its own git setup during the run and leaves those unusable, so the later push has no valid auth. The commit and no-op-skip logic were correct; only the push auth was wrong.Fix: push through an
x-access-token:<workflow-token>URL (masked in logs), so the push carries its own auth regardless of what the agent step left in the git config.Workflow-only change, no changeset. Verifies after merge (workflow-validation gate): I'll re-run the two-turn test and confirm
readCodereads the pushed file and turn 2 builds on turn 1's branch.Refs #1085 #1087