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

One template per branch #4

Open
ltetrel opened this issue Feb 23, 2022 · 3 comments
Open

One template per branch #4

ltetrel opened this issue Feb 23, 2022 · 3 comments

Comments

@ltetrel
Copy link
Member

ltetrel commented Feb 23, 2022

Each branch can contain one template example.
This helps centralize all templates in one place. Not sure to what extent it is possible to create a new repo based on template branches, or if it takes just the main branch.

@emdupre
Copy link
Member

emdupre commented Mar 17, 2022

If we ask users to fork the template repo, it will come with all included branches and then they'll be able to select the one they want to work off of by e.g. cloning only the desired branch.

I'm not sure if the extra (potential) user confusion is worth the de-cluttering, IMHO. But definitely something to discuss !

@ltetrel
Copy link
Member Author

ltetrel commented Mar 17, 2022

thx for feedback @emdupre
So I am also questioning how github can manage template branches using the github interface (green button "use this template").

Yes, we need anyway to work on the templates. For now we have one template for python: https:/neurolibre/template.
If we want one template per repo, then we need to rename it.
Ideally I see few other templates like:

  • octave (with dockerfile)
  • repo2data

@emdupre
Copy link
Member

emdupre commented Mar 18, 2022

Ah, thanks for clarifying ! From my read of the GitHub template docs, the behavior around branches is really to pull all branches or just the default one, with the UX encouraging the latter behavior.

So, if we wanted the user to pull from a specific, non-default branch, they'd need to first select "Include all branches" (e.g. here) and then follow the usual git checkout workflow.

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