-
Notifications
You must be signed in to change notification settings - Fork 20
Closed as not planned
Labels
enhancementNew feature or requestNew feature or requestrevisit sometimeUseful to address but no bandwidth at the momentUseful to address but no bandwidth at the moment
Description
Context
Currently, the only way to discover which pathogen repos are available for setup is to individually inspect nextstrain-pathogen.yaml files in pathogen repos.
Proposal
Design discussions happened in a Google Doc. Here is an example snippet:
$ nextstrain list
Runnable:
measles
measles@local {ingest, phylogenetic, nextclade}
measles@main {ingest, phylogenetic, nextclade}
zika
zika@main (default) {ingest, phylogenetic}
zika@local {ingest, phylogenetic, nextclade}
Available for setup:
mumps@main {ingest, phylogenetic, nextclade}
<https://github.com/nextstrain/mumps>
ncov-ingest@master {manual-upload}
<https://github.com/nextstrain/ncov-ingest>
nipah@main {ingest, phylogenetic}
<https://github.com/nextstrain/nipah>Progress
Reactions are currently unavailable
Pinned by victorlin
Pinned comment options
I chatted with Jover about this 1:1 a couple weeks ago. We concluded that, given the relatively low priority of rolling out nextstrain run support to more pathogen repos, making a command to list available repos is also low priority.
We can still consider a new command to list locally set up pathogen repos. I've created a new issue for that: #510
Metadata
Metadata
Assignees
Labels
enhancementNew feature or requestNew feature or requestrevisit sometimeUseful to address but no bandwidth at the momentUseful to address but no bandwidth at the moment