Skip to content

DOC: Pandas Contribution Documentation: Forking Instructions #16419

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

Closed
puifais opened this issue May 22, 2017 · 1 comment · Fixed by #17751
Closed

DOC: Pandas Contribution Documentation: Forking Instructions #16419

puifais opened this issue May 22, 2017 · 1 comment · Fixed by #17751
Labels
Milestone

Comments

@puifais
Copy link

puifais commented May 22, 2017

Problem description

As a newbie contributing to an open source project for the first time, I find the instruction for forking a little difficult to follow. Specifically, on this line

git clone git@github.com:your-user-name/pandas.git pandas-yourname

Output of git clone [email protected]:your-user-name/pandas.git pandas-yourname

Permission denied (publickey). fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

I was able to clone the repository by using the following code

git clone https://github.com/your-user-name/pandas.git pandas-yourname

Expected Output

Cloning into 'pandas-username'... remote: Counting objects: 124979, done. remote: Total 124979 (delta 0), reused 0 (delta 0), pack-reused 124978 Receiving objects: 100% (124979/124979), 96.04 MiB | 1.89 MiB/s, done. Resolving deltas: 100% (103137/103137), done.

I am hesitant on how best to edit the documentation because I know that for people who are more experience, they know automatically to set up a key when they see the [email protected]:your-user-name/ part

@puifais puifais changed the title Pandas Contribution Documentation: Forking Instructions DOC: Pandas Contribution Documentation: Forking Instructions May 22, 2017
@TomAugspurger
Copy link
Contributor

I think your change makes sense (I usually use https)

Want to make a pull request updating that file?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants