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 joverlee521 force-pushed the nextstrain-run-workflows branch from 13e2522 to 0cfa91e Compare September 26, 2025 22:52
@joverlee521 joverlee521 marked this pull request as ready for review September 26, 2025 22:53
@joverlee521
Copy link
Contributor Author

Tested with Nextstrain CLI 10.3.0

$ nextstrain setup zika@nextstrain-run-workflows
Setting up zika@nextstrain-run-workflows…
Using existing setup in '/Users/joverlee/.nextstrain/pathogens/zika/nextstrain-run-workflows=NZSXQ5DTORZGC2LOFVZHK3RNO5XXE23GNRXXO4Y='.
  Hint: if you want to ignore this existing setup, re-run `nextstrain setup` with --force.

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

Note that your pathogen default version is still zika@main.

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

    nextstrain run zika@nextstrain-run-workflows …

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

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

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

@joverlee521 joverlee521 merged commit 873c54b 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