#87 Fix issues regarding whitespaces and different file separators in ssh-key file path #106
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
- On linux these tests run successfully. Maybe this is an OS dependant problem?
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
…e it with a testcontainer repository
…o ignore strictHostKeyChecking, add test to check release workflow with authentication
…ferent formats of slashes
…he temporary directory on linux
simonhauck
force-pushed
the
87-ssh-key-file-path-with-whitespaces-does-not-work
branch
from
f0abd28 to
e32e2fa
Compare
simonhauck
changed the title
simonhauck
deleted the
87-ssh-key-file-path-with-whitespaces-does-not-work
branch
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.
Fix issues regarding whitespaces in ssh-key file path
Correctly escape paths with a \ on windows