Skip to content
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

Why not fork and clone? #65

Closed
mbeyeler opened this issue Jun 28, 2017 · 2 comments
Closed

Why not fork and clone? #65

mbeyeler opened this issue Jun 28, 2017 · 2 comments

Comments

@mbeyeler
Copy link
Member

I am confused about the following bit in the instructions:

To use this repository as a template, start by cloning it to your own computer under the name you will want your project to have:

git clone https://github.com/uwescience/shablona smallish
cd smallish

To point to your own repository on github you will have to issue something like the following:

git remote rm origin
git remote add origin https://github.com/arokem/smallish

(replace arokem with your own Github user name).

Why not just fork and clone? It seems that's what you are trying to achieve anyway by removing origin and adding a new remote.

@arokem
Copy link
Contributor

arokem commented Jun 28, 2017

You can only fork a repository once, and Github will retain the forking relationship with that repo, unless you write them and ask them to disconnect this relationship.

That said, this is indeed clunky, and what we should actually do here is explain how to use the Github importer: https://github.com/new/import

@arokem
Copy link
Contributor

arokem commented Aug 29, 2017

Addressed in #68

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

No branches or pull requests

2 participants