Skip to content
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.

Sign up for GitHub

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

Jump to bottom

ingest: Move Nextclade configs to separate YAML #34

Merged
merged 1 commit into from
Mar 7, 2024
Merged

ingest: Move Nextclade configs to separate YAML #34

merged 1 commit into from
Mar 7, 2024

Commits on Feb 26, 2024

  1. ingest: Move Nextclade configs to separate YAML 

    It is unintuitive to have to remove default configs on the first run
of the ingest workflow, so move the Nextclade configs to a separate
config YAML that can be optionally used in `nextstrain build`.

Note that once the Nextclade dataset is stabilized for a pathogen,
it then makes sense to move the configs into the default config.yaml
    @joverlee521
    joverlee521 committed Feb 26, 2024
    Configuration menu
    Copy the full SHA
    4dd4c64 View commit details
    Browse the repository at this point in the history