Users can only fork a project once - default method should be create_new_project.sh ?

[magic-lantern]

@callahantiff and @tuh8888 - So I'm working on a new project for which I want to use Abra-Collaboratory. However, I just realized that users can only fork a project once! Due to the single fork limitation, it seems that it would be better to recommend the create_new_project.sh script created by @tuh8888 as the default instructions.

As I recall, I previously thought that forking would be easier to do, however, now that I'm wanting 2 Abra-Collaboratory based projects, I see forking is a problem. I think the fork directions could still be preserved, but should have a large warning added that you can only fork once.

[magic-lantern]

I just found out about a new github feature (announced in June 2019) - repository templates. Haven't tried it yet, but in reading the description, it may solve the fork limitation and be easier than running a shell script:

https://github.blog/2019-06-06-generate-new-repositories-with-repository-templates/

[callahantiff]

@magic-lantern - thanks for all of the great info! The repo templates certainly look awesome, otherwise, the approach @tuh8888 initially suggested as sounds works for me.

I am slammed with two conference submissions, a job interview, and a workshop between now and September 9th. Happy to help make these changes then. I'm sorry to not be able to do them earlier, if you either of you feel comfortable making these changes (prioritizing the repo templates) and would like them done before September, please feel free to move ahead without me! 😄

[magic-lantern]

@callahantiff - Best of luck with your conference submissions, job interviews, etc. I'm also pretty busy for the next few weeks, but should have time in the later half of August to investigate some of these options proposed here.

[callahantiff]

@callahantiff - Best of luck with your conference submissions, job interviews, etc. I'm also pretty busy for the next few weeks, but should have time in the later half of August to investigate some of these options proposed here.

Thanks @magic-lantern, good luck with your work as well. I will check back in a few weeks. Thanks again for pointing out these resources and continuing to support this work, I am so appreciative of your help! 🙇‍♀

[magic-lantern]

I did some more exploration of the new template functionality. Converting an existing repo to a "template" is very easy:

https://help.github.com/en/articles/creating-a-template-repository

Creating a repository from a template is very easy too - and you can create as many as you want. See https://help.github.com/en/articles/creating-a-repository-from-a-template

The operation can also be undone, but any projects created by "Using this template" are not affected by the change.

Multiple "Use this template" operations can be done.

There are a few manual steps that will need to be taken if using the "template" option:

• Wikis are not copied.
• Project boards are not copied.

For both of the above, the existing manual or scripted process still works.

If you'd like to see the template project I created (cloned from the base Abra-Collaboratory
using the create_new_project.sh script), take a look at https://github.com/magic-lantern/testing or one of the template clones at https://github.com/magic-lantern/anothertemplate