Repository navigation
Fix git push auth: revert to URL rewriting, add token redaction - #27
Merged
Merged
Conversation
The ephemeral -c http.extraheader approach failed in CI. Revert to the proven URL rewriting approach but add token redaction on errors so the token is never exposed in CI logs. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Collaborator
|
The changes in this PR will be included in the next version bump.
|
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
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
-c http.extraheaderapproach from Harden security across publishing, auth, and input validation #24 didn't work withexecFileSyncin CI, causing the push to fail and leaking the token in the error messagefinally)Test plan
bumpy ci releasesuccessfully pushes the version PR branch🤖 Generated with Claude Code