PGO update script: Connect to GitHub over HTTPS rather than SSH. #11814
+1
−1
Conversation
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
![copybara-service[bot]](https://avatars.githubusercontent.com/in/44061?s=60&v=4){kind=small}
The `gh auth setup-git` command appears to configure Git as a credential helper for `https`, not for SSH-based access. SSH access fails with the host authenticity check. Try to connect over HTTPS instead, to see if that works properly. Otherwise we will have to provision `~/.ssh/known_hosts` and give the agent a private SSH key for authentication. PiperOrigin-RevId: 771259063
copybara-service
bot
force-pushed
the
test/cl771259063
branch
from
0832542 to
a56ad99
Compare
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.
PGO update script: Connect to GitHub over HTTPS rather than SSH.
The
gh auth setup-gitcommand appears to configure Git as a credentialhelper for
https, not for SSH-based access. SSH access fails with thehost authenticity check.
Try to connect over HTTPS instead, to see if that works properly.
Otherwise we will have to provision
~/.ssh/known_hostsand give theagent a private SSH key for authentication.