Skip to content

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

Merged
merged 5 commits into from Oct 14, 2020
Merged

Replace ssh with https #18229

merged 5 commits into from Oct 14, 2020

Conversation

ghost
Copy link

@ghost ghost commented Oct 10, 2020

Modify the git remote add fork argument in perlhack.pod.

@Grinnz
Copy link
Contributor

Grinnz commented Oct 10, 2020

Why?

This part of the documentation is describing your personal fork, which you need to set up with write access.

@ghost
Copy link
Author

ghost commented Oct 10, 2020

SSH URLs are not mentioned in perlhack.pod.

617d9ec#diff-fbf8c7e20f85f9aacf05c038ed8c687d
Update perlgit and perlhack to reference GitHub pull request workflow
khwilliamson committed Oct 24, 2019

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
Update documentation, comments, metadata to reference GitHub as canon…
toddr committed Oct 20, 2019

perlhack.pod

-  % git clone git://perl5.git.perl.org/perl.git perl
+  % git clone https://github.com/Perl/perl5.git perl

@Grinnz
Copy link
Contributor

Grinnz commented Oct 10, 2020

That does not answer the question.

@Leont
Copy link
Contributor

Leont commented Oct 10, 2020

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.

@Grinnz
Copy link
Contributor

Grinnz commented Oct 11, 2020

It is not a preference. The remote added for your personal fork must have write access.

@xenu
Copy link
Member

xenu commented Oct 11, 2020

You can have write access via https, github supports that.

@Grinnz
Copy link
Contributor

Grinnz commented Oct 11, 2020

Only via explicit credentials, but I suppose if you want to explain both that option and ssh keys.

@Grinnz
Copy link
Contributor

Grinnz commented Oct 11, 2020

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.

@ghost
Copy link
Author

ghost commented Oct 11, 2020

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.

% git remote add fork [email protected]:MyUser/perl5.git

For more information, see "Connecting to GitHub with SSH".

If you'd rather use an HTTPS URL for your git push see "Cloning with HTTPS URLs".

% git remote add fork https://github.com/MyUser/perl5.git

Then, push your new branch to your fork.

@Grinnz
Copy link
Contributor

Grinnz commented Oct 12, 2020

The current addition is reasonable.

Copy link
Member

@atoomic atoomic left a 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 :-)

@ghost
Copy link
Author

ghost commented Oct 13, 2020

Opening this ticket was not a matter of personal preferences.

When creating a repository via GitHub's menu subsequent instructions use HTTPS URLs.

@khwilliamson khwilliamson merged commit b998bd1 into Perl:blead Oct 14, 2020
@ghost ghost deleted the perlhack-https branch October 14, 2020 03:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants