disable strict host checking with a flag #7
Merged
Conversation
This file contains 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
mishamo
approved these changes
Sep 29, 2022
adamdougal
reviewed
Sep 29, 2022
Co-authored-by: Adam Dougal <[email protected]>
adamdougal
approved these changes
Nov 4, 2022
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.
When running vergo on CI (and locally without github as an entry to known_hosts) we were getting the error:
This can be fixed by running the command:
ssh-keyscan -H github.com >> ~/.ssh/known_hostsThere should be no need to run this on CI as this is not cached, therefore this PR adds a new flag to disable strict host checking with the suggetion to only using this on CI.