Skip to content

Conversation

@joverlee521
Copy link
Contributor

Description of proposed changes

An alternative to #327, where instead of maintaining a separate Snakefile per named phylo workflow, we just define the phylo workflows in the nextstrain-pathogen.yaml. Depends on CLI changes in nextstrain/cli#462.

Checklist

  • Checks pass
  • Update changelog

@joverlee521 joverlee521 force-pushed the nextstrain-run-workflows branch 2 times, most recently from 94b2159 to d7722ce Compare July 23, 2025 22:50
Use the `nextstrain-pathogen.yaml` to declare the ingest workflow as a 
`nextstrain run` compatible workflow. 

Requires changes from <nextstrain/cli#461> to 
properly list the workflow in the Nextstrain CLI outputs.
Mostly workflow path updates to support `nextstrain run`. This should allow 
the default phylogenetic build to run with 
`nextstrain run mpox phylogenetic <analysis-dir>`. The following commit will 
add support for the other builds.
Use the `nextstrain-pathogen.yaml` to list the available phylogenetic 
workflows for `nextstrain run`. 

Requires changes from <nextstrain/cli#462>
to properly use the correct Snakefile and configfile for each workflow.
@joverlee521 joverlee521 force-pushed the nextstrain-run-workflows branch from 57e52de to 9cac7a4 Compare July 30, 2025 18:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants