fix: resolve duplicate Authorization header in release workflow#1154
Merged
Conversation
Deploying kitops-org with
|
| Latest commit: |
8cbb544
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://8fe0224b.kitops-org.pages.dev |
| Branch Preview URL: | https://fix-release-duplicate-auth-h.kitops-org.pages.dev |
gorkem
force-pushed
the
fix/release-duplicate-auth-header
branch
from
dd61684 to
f24e344
Compare
Checkout with the GitHub App token directly instead of manually setting http.extraheader after checkout. The previous approach added a second Authorization header on top of the one persisted by actions/checkout, causing GitHub to reject git fetches with HTTP 400. Signed-off-by: Gorkem Ercan <gorkem.ercan@gmail.com>
gorkem
force-pushed
the
fix/release-duplicate-auth-header
branch
from
f24e344 to
8cbb544
Compare
amisevsk
approved these changes
Apr 2, 2026
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
The release workflow's "Generate CLI documentation" step was failing with
HTTP 400: Duplicate header: "Authorization"duringgit fetch origin main.actions/checkoutpersists git credentials (Authorization header) automatically. The workflow then manually added a second Authorization header viagit config --local http.extraheaderfor the GitHub App token, resulting in two headers being sent.Fix: Move the App token generation before checkout and pass it via
token:so checkout persists the correct credentials from the start. Removes the manualgit config --local http.extraheadercall entirely.