A few weeks ago GitHub announced that you can mark repositories as “template repositories”: https://github.blog/2019-06-06-generate-new-repositories-with-repository-templates/
This makes it easier for people to use a repository as a starting point for a new repo. I think in the past a lot of people cloned a repo and then edited it when they wanted a template.
Related to An interactive Binder config file builder GUI I was thinking we could/should create some template repositories for use with repo2docker and BinderHubs.
Should we convert the example repos under github.com/binder-examples or create dedicated ones?
I was thinking of creating three templates:
- Python with pip: uses
requirements.txt, gives advice on how to pin (or not) dependencies, has a empty
postBuildcontaining a comment about what you can do here,
runtime.txtto select Python version, badges to launch Jupyter notebook and Jupyter lab
- Python with conda: uses
environment.yml, mention how to select Python version, gives advice on how to pin (or not) dependencies, empty
postBuildwith comment, badges to launch Jupyter notebook and Jupyter lab
- R with
install.R, explain MRAN date and
postBuildwith comment, badge that launches R Studio
These seem like the most frequent use cases for beginners/people discovering repo2docker.