You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I started creating a repo from the template but, as soon as the repo gets created, GitHub starts creating a release with the files contained in the template.
I was wondering if it would not be better to have a clean template (singularity-deploy) with only the workflow and a "example" repo (singularity-deploy-helloworld) which forks the clean template and shows how to use it.
In the README of the "helloworld" repo you can describe how to fork or start from the "singularity-deploy" template.
The text was updated successfully, but these errors were encountered:
I was also thinking about removing the "VERSION" file from the template but your update works as well. What I forgot to mention is that having a clean template with only the workflow would allow to keep it in sync after a fork. Otherwise if you start changing the recipes, I pretty sure it will complain when trying to merge possible updates of the workflow from the template.
I started creating a repo from the template but, as soon as the repo gets created, GitHub starts creating a release with the files contained in the template.
I was wondering if it would not be better to have a clean template (singularity-deploy) with only the workflow and a "example" repo (singularity-deploy-helloworld) which forks the clean template and shows how to use it.
In the README of the "helloworld" repo you can describe how to fork or start from the "singularity-deploy" template.
The text was updated successfully, but these errors were encountered: