@manics That “symlink” approach would work for me
Just trying to think of a way where a user can easily say:
- use this branch for the Binder image;
- use this branch for the nbgitpull;
- use the referrer as the location of the repo.
I guess things start to get even more complicated if you have the image builder branch and the content branch in different repos…!
However, if you enforce a convention, things get easier; eg easiest for magic to work might be:
- content repo must be in
- Binder build repo
must be in
binder-build and must include
- both branches need to be branches of the same repo.
But being able to pop a link into a simple environment file to specify eg the Binder image branch would make sense (you wouldn’t want the link in the Binder build branch because that’s the one we’re trying not to change at at all).
Thinking back on the template repo idea, if a template repo:
- has a Binder image build branch;
- has an autodetect path in the README binder button link;
- has a reference that points back to the build branch using an absolute URL
a user could derive a repo from the template, update the content file, click the button, launch against the Binder image specified originally in the template repo.
Alternatively, you could clone a repo containing a content (master) branch and a build branch and specify the build branch relatively from within the content repo.