fix: use remote URL token embedding for git push auth#74
Merged
Conversation
The extraheader-only approach introduced in 7e92e5b doesn't work with actions/checkout@v6 which no longer persists credentials by default. Switch withGitToken to embed the token in the remote URL instead, matching the approach that was previously working in pushWithToken.
|
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
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.
Summary
actions/checkout@v6which no longer persists credentials by defaultwithGitTokento embed the token in the remote URL (https://x-access-token:TOKEN@...) instead, matching the approach that was previously working inpushWithTokenTest plan