-
Notifications
You must be signed in to change notification settings - Fork 577
Replace ssh with https #18229
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Replace ssh with https #18229
Conversation
Why? This part of the documentation is describing your personal fork, which you need to set up with write access. |
SSH URLs are not mentioned in perlhack.pod. 617d9ec#diff-fbf8c7e20f85f9aacf05c038ed8c687d perlhack.pod - % git format-patch -1
- % ./perl -Ilib utils/perlbug -p 0001-*.patch
+ % git remote add fork [email protected]:MyUser/perl5.git A git protocol clone was previously replaced with an https clone. 47ef154#diff-fbf8c7e20f85f9aacf05c038ed8c687d perlhack.pod - % git clone git://perl5.git.perl.org/perl.git perl
+ % git clone https://github.com/Perl/perl5.git perl |
That does not answer the question. |
Different people have different preferences. I can see the argument for mentioning both ways, but simply changing it to your preference seems like an unfortunate move. |
It is not a preference. The remote added for your personal fork must have write access. |
You can have write access via https, github supports that. |
Only via explicit credentials, but I suppose if you want to explain both that option and ssh keys. |
If you want to mention both options, it would be best to link to https://docs.github.com/en/free-pro-team@latest/github/using-git/which-remote-url-should-i-use and indicate that authentication with either SSH keys or personal access token is required to push to your private fork. |
Create a GitHub fork of the perl5 repository and add it as a remote, if you haven't already, as described in the GitHub documentation at https://help.github.com/en/articles/working-with-forks.
For more information, see "Connecting to GitHub with SSH". If you'd rather use an HTTPS URL for your
Then, push your new branch to your fork. |
The current addition is reasonable. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, at least this leaves the choice to the user to use ssh or https :-)
Opening this ticket was not a matter of personal preferences. When creating a repository via GitHub's menu subsequent instructions use HTTPS URLs. |
Modify the
git remote add fork
argument in perlhack.pod.