Skip to content

Conversation

@jorgee
Copy link
Contributor

@jorgee jorgee commented Nov 21, 2025

close #5890
This pull request updates the pipeline run logic to handle cases where the pipeline is specified in a subfolder of the URLs. The main changes involve passing the main script file to the AssetManager, updating its constructor and build method, and adding validation to prevent script files from being used as repository URLs.

Supported case:

$ nextflow run https://github.com/ekageyama/nextflow_sub -main-script pipeline/main.nf

 N E X T F L O W   ~  version 25.10.0

Pulling ekageyama/nextflow_sub ...
WARN: Cannot read project manifest -- Cause: Remote resource not found: https://api.github.com/repos/ekageyama/nextflow_sub/contents/nextflow.config
 downloaded from https://github.com/ekageyama/nextflow_sub.git
Launching `https://github.com/ekageyama/nextflow_sub` [stoic_wilson] DSL2 - revision: b409fabb25 [main]

executor >  local (2)
[7b/920f71] convertToUppercase | 1 of 1 ✔
[01/a45652] addPrefix          | 1 of 1 ✔
Pipeline completed at: 2025-11-21T19:49:05.875003740+01:00
Execution status: SUCCESS

However, it is not supporting passing the full URL path to the main script. The path parts dedicated to identify the repository depends on the type. The github case can be inferred, because they are always two, but not for the rest. Gitlab/Bitbucket/Gitea can be hosted and Azure can include 2 o 3 path parts. In this cases, now it prints this error

$ dev_nextflow run https://github.com/ekageyama/nextflow_sub/pipeline/main.nf

 N E X T F L O W   ~  version 25.10.0

Repository URL can end as a script file (.nf|.nxf) - Use -main-script option.

TODO:

Signed-off-by: jorgee <jorge.ejarque@seqera.io>
@jorgee jorgee linked an issue Nov 21, 2025 that may be closed by this pull request
@netlify
Copy link

netlify bot commented Nov 21, 2025

Deploy Preview for nextflow-docs-staging canceled.

Name Link
🔨 Latest commit c641d6f
🔍 Latest deploy log https://app.netlify.com/projects/nextflow-docs-staging/deploys/6920bc47f50eaf0007df3d7e

@bentsherman
Copy link
Member

Undefined nextflow.config: should we look at repo root or in the main.nf location

It should look for nextflow.config in the same directory as the main script

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Running pipelines from a git-repo with a main.nf doesnt work

3 participants