On Fri, Nov 10, 2017 at 1:19 PM Tony Hirst <[email protected]> wrote:
> Hmm... I'd tried with --ref BRANCH but that just gave a fatal error: > > Eg, for https://github.com/USER/REPO/tree/BRANCH, running: > > jupyter-repo2docker https://github.com/USER/REPO --ref BRANCH > > gives: > > unknown revision or path not in the working tree > > Indeed, also fails for me. I think that is a bug: https://github.com/jupyter/repo2docker/issues/135 As a workaround (actually tried it before recommending it ...) you can put the SHA of the commit on the branch. T -- You received this message because you are subscribed to the Google Groups "Project Jupyter" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jupyter/CAN3x1RZO-0A%3D7QZVe0ojPeYCKkoehSq2h%2BsodvDy5V0QwB17Lg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
