Skip to content

Conversation

@joverlee521
Copy link
Contributor

@joverlee521 joverlee521 commented Sep 23, 2025

Description of proposed changes

Depends on merge and release of nextstrain/cli#472

Requires Nextstrain CLI 10.3.0

Checklist

  • Checks pass
  • Update changelog

@joverlee521
Copy link
Contributor Author

Tested with Nextstrain CLI 10.3.0

$ nextstrain setup mumps@nextstrain-run-workflows
Setting up mumps@nextstrain-run-workflows…
Extracted 137 files and directories to '/Users/joverlee/.nextstrain/pathogens/mumps/nextstrain-run-workflows=NZSXQ5DTORZGC2LOFVZHK3RNO5XXE23GNRXXO4Y='.

Checking setup…
✔ yes: downloaded
✔ yes: contains nextstrain-pathogen.yaml
✔ yes: nextstrain-pathogen.yaml declares `nextstrain run` compatibility
✔ yes: `nextstrain run` workflow 'ingest' exists
✔ yes: `nextstrain run` workflow 'phylogenetic' exists
✔ yes: `nextstrain run` workflow 'nextclade' exists

Warning: No pathogen default version is configured and no implicit default is intuitable.

You can use mumps@nextstrain-run-workflows on an ad-hoc basis by specifying it
explicitly, e.g.:

    nextstrain run mumps@nextstrain-run-workflows …

If you want to use mumps@nextstrain-run-workflows by default instead, re-run
this command with the --set-default option, e.g.:

    nextstrain setup --set-default mumps@nextstrain-run-workflows            

All good!  Set up of mumps@nextstrain-run-workflows complete.

@joverlee521 joverlee521 merged commit 53c0a6e into main Sep 26, 2025
4 checks passed
@joverlee521 joverlee521 deleted the nextstrain-run-workflows branch September 26, 2025 23:12
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