ACM-37051: fix: prevent duplicate Authorization header in merge workflow#150
Merged
Merged
Conversation
…Authorization headers The create-pull-request action sets its own git credential for pushing to the fork repo. With actions/checkout@v7 persisting its GITHUB_TOKEN credential via includeIf.gitdir, both resolve when contacting github.com, causing a "Duplicate header: Authorization" HTTP 400 error. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
coleenquadros
changed the title
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
2 participants
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
persist-credentials: falsetoactions/checkout@v7in the merge workflowDuplicate header: "Authorization"HTTP 400 error when the create-pull-request action pushes to the sandbox forkRoot cause
actions/checkout@v7persists its GITHUB_TOKEN credential viaincludeIf.gitdirin the git config. Whenrhobs/acm-create-pull-request@push-to-fork-tokenlater sets its own GitHub App token credential, both resolve forgithub.com, causing git to send twoAuthorizationheaders. GitHub rejects this with HTTP 400.Why now
This started after
actions/checkoutwas bumped from v6 to v7 in #146. Checkout v7 changed how credentials are persisted — it now uses a separate credentials file included viaincludeIf.gitdir, which stacks with (rather than being overwritten by) the create-pull-request action's local config credential.Test plan
🤖 Generated with Claude Code