This repository has been archived by the owner on Jan 15, 2024. It is now read-only.
fix: Use HTTPS instead of GIT protocol for cloning #57
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
Since 2022-01-11, GitHub has deprecated the usage of the git:// protocol in favour of the more secure https:// — cf. https://github.blog/2021-09-01-improving-git-protocol-security-github/#no-more-unauthenticated-git This causes the following error when, e.g., cloning this repo as submodule: > The unauthenticated git protocol on port 9418 is no longer supported. > Please see > https://github.blog/2021-09-01-improving-git-protocol-security-github/ > for more information. As suggested in https://stackoverflow.com/a/70663683/5433628 we have then replaced URLs using git:// by their https:// equivalent. Signed-off-by: Étienne Boisseau-Sierra <etienne.boisseau-sierra@unipart.io>
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Overview
Since 2022-01-11, GitHub has deprecated the usage of the git:// protocol
in favour of the more secure https:// — cf.
https://github.blog/2021-09-01-improving-git-protocol-security-github/#no-more-unauthenticated-git
This causes the following error when, e.g., cloning this repo as
submodule:
As suggested in https://stackoverflow.com/a/70663683/5433628 we have
then replaced URLs using git:// by their https:// equivalent.
Related issues
n/a