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
My repository is private.
It has a submodule which is also private.
I specify the credentials in SCM configuration file. nextflow pull repo/pipeline
pulls the pipeline but not the submodule.
Expected behavior and actual behavior
(Submodules should be authenticated)
Steps to reproduce the problem
(By definition, it is a bit difficult to share private repositories)
Confirming this with 19.0.0.modules-draft10-SNAPSHOT, with the caveat that in my case it does not attempt to download the submodules. (for me too, both parent and child repo are private)
This will become a more important issues when Nextflow modules are finalized, since a natural way to distribute modules will be through git submodule.
Bug report
My repository is private.
It has a submodule which is also private.
I specify the credentials in SCM configuration file.
nextflow pull repo/pipeline
pulls the pipeline but not the submodule.
Expected behavior and actual behavior
(Submodules should be authenticated)
Steps to reproduce the problem
(By definition, it is a bit difficult to share private repositories)
Program output
Where
repo/data
is included as a submodule inrepo/pipeline
.Environment
Additional context
Contents of
.gitmodules
:Note: changing the authentication from git to https, ie changing the url to
https://github.com/repo/data.git
and makingdata
pubic works. Obviously.The text was updated successfully, but these errors were encountered: