Add proposed subclades to public and private builds #195
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description of proposed changes
Updates the workflow configs, scripts, and rules to use proposed subclades instead of subclades in private builds and adds proposed subclades to public builds for all three lineages and both HA and NA.
As part of this update, I've also updated the color scales for subclades to reflect the variants circulating in the last 6 months with two or more sequences in the most recent public 2y builds.
Related issue(s)
Replaces #193
Follows from #194
Related to nextstrain/augur#1661
Checklist