Fork and clone may not be the best workflow about jupyter-book HOT 6 CLOSED

@arokem could explain more what you mean by "GitHub import"? I agree fork+clone is not the most ideal but wasn't sure how else to accomplish this.

from jupyter-book.

Oh sorry -- should have provided a link: https://github.com/new/import

This allows you to create an exact copy of a repository, but without the forking relationship.

I know about this easter egg because that's what we use to create workshop websites for Carpentries' workshops.

Thanks for your work on this, by the way! It looks great!

from jupyter-book.

that's pretty cool! I'll try and add it in to the guide somewhere

from jupyter-book.

This repo now suggests that people use your suggested "github import" method for getting their version of the repository, that now lives in the guide here:

http://predictablynoisy.com/textbooks-with-jupyter/guide/02_setup/#get-your-own-copy-of-this-repository

what do you think?

from jupyter-book.

Looks great! I added a small suggestion in #15

from jupyter-book.

Closing this one.

from jupyter-book.