-
Notifications
You must be signed in to change notification settings - Fork 621
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
Clone/Pull submodules recursively #1615
Conversation
Signed-off-by: Akira Sekiguchi <[email protected]>
9ab6460
to
8f475f4
Compare
modules/nextflow/src/main/groovy/nextflow/scm/AssetManager.groovy
Outdated
Show resolved
Hide resolved
2bcb845
to
8447dfd
Compare
Signed-off-by: Akira Sekiguchi <[email protected]>
8447dfd
to
c8cc08e
Compare
Signed-off-by: Akira Sekiguchi <[email protected]>
f67871a
to
13d9961
Compare
Hi, Paolo, I have added |
This looks doable, however currently submodules are controlled via the config file setting the attribute For consistency, I would suggest adding
Would that work for you? |
Thank you for your comment, Paolo. |
No hurry! |
Signed-off-by: Akira Sekiguchi <[email protected]>
be9bd52
to
4d888b1
Compare
Hi, Sorry to be late, but I have changed the code to control the recursive behavior from manifest scope. I hope it is acceptable. Thanks. |
Nice thanks! |
Hello,
I found
run
command fails to download the codes of submodule of submodule (the grand daughter module) from the repository.pull
andclone
commands even fail to download the codes of submodule (the daughter module).For most of the nextflow users need the submodules downloaded recursively when they
run
their scripts. So this is my attempt to achieve it.version 20.05.0-SNAPSHOT build 5335
created 10-05-2020 21:32 UTC (11-05-2020 06:32 JDT)