We can remove a lot manual work by adding GH Action workflows to run workflows.
The GH Action for fauna ingest will most likely need to be manually triggered since we still need to upload data to fauna manually. However, the GH Action for NCBI + Andersen lab ingest can be scheduled to run automatically.
I'm not as familiar with the phylogenetic workflows in this repo, so it's unclear to me how much we can automate them via GH Actions. Is there a lot of manual clean up that needs to be done for builds or is it as straightforward as running nextstrain build and then nextstrain deploy?
Follow up to https://github.com/nextstrain/avian-flu/pull/40. Blocked by https://github.com/nextstrain/avian-flu/issues/41
We can remove a lot manual work by adding GH Action workflows to run workflows.
The GH Action for fauna ingest will most likely need to be manually triggered since we still need to upload data to fauna manually. However, the GH Action for NCBI + Andersen lab ingest can be scheduled to run automatically.
Both GH Action workflows should use the shared pathogen-repo-build workflow. This will depend on https://github.com/nextstrain/infra/issues/11 for using OIDC tokens in the GH Action workflow.
I'm not as familiar with the phylogenetic workflows in this repo, so it's unclear to me how much we can automate them via GH Actions. Is there a lot of manual clean up that needs to be done for builds or is it as straightforward as running
nextstrain buildand thennextstrain deploy?