Change git remote paths from HTTPS to SSH #502
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
hombit
force-pushed
the
git-ssh
branch
2 times, most recently
from
92da049 to
eb58ed4
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.
Change Description
Usually, SSH git URLs are used for remotes when working from the terminal. This PR proposes to change the suggested
git remote addcommand to use SSH paths instead of HTTPS paths.However, I'm not sure about other use cases: GUI clients, VS Code, etc.
Checklist
lincc-frameworks/python-project-templaterepo and not a downstream one instead.