You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My desire would be for every nextclade dataset to be represented at /nextclade. Right now I find myself going to clades.nextstrain.org and picking a reference pathogen and example dataset if I want to see the nextclade reference tree for a particular nextclade dataset. I don't know how easy including an automated push to data.nextstrain.org as part of the release process for nextclade datasets would be. Having these pushed to data.nextstrain.org would have the added benefit of easily looking at past versions, eg https://nextstrain.org/nextclade/sars-cov-2@2024-01-01 cc @rneher and @corneliusroemer
@victorlin: My sense is that a tile that says SARS-CoV-2 (Nextclade) is a fine solution for your PR. It may get revised to Nextclade in the future.
continuing from #940 (comment):
Requirements
The text was updated successfully, but these errors were encountered: