fix: put docs token in password slot so git push authenticates#758
Merged
Conversation
The clone URL placed the token in the username slot with no password, so git push prompted for a password and failed on CI (exit 128). Use x-access-token: so the token lands in the password slot.
divolgin
approved these changes
Jun 29, 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.
The docs job on release fails at
git pushwith exit 128 (could not read Password). The clone URL puts the token in the username slot with no password, so the push can't authenticate non-interactively. Cloning still works becausereplicated-docsis public.Fix: use
x-access-token:${GITHUB_TOKEN}so the token lands in the password slot. No token rotation needed.