-
Notifications
You must be signed in to change notification settings - Fork 19
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.
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
Rename repo & builds #168
Comments
Lots of progress here - I've updated the task list. @corneliusroemer is there anything else you can think of? |
I think that sounds good. Next step would be repo rename? Let's do it one at a time to be able to know what broke it in case something breaks |
@corneliusroemer sounds good! Would you be able to do that whenever's good for you to monitor breakage? I'll be signing off soon and will be busy most of tomorrow. |
Repo rename done by @trvrb (Slack thread). I'll look into updating existing references. |
Related-to: <nextstrain/mpox#168>
Related-to: <nextstrain/mpox#168>
Related-to: <nextstrain/mpox#168>
Related-to: <nextstrain/mpox#168>
I updated the task list in the issue description, and I think everything is done here. Please re-open if you notice anything that was missed. |
Context
General naming recommendations are continuing to depreciate (and expected to depreciate further) using 'monkeypox'. We likely should replace 'monkeypox' with 'MPXV' (and possibly Mpox in some places). This will require:
/monkeypox
to/mpox
nextstrain.org#713nextstrain/monkeypox
isn't created)mpox
in path: Rename instances of "monkeypox" to "mpox" #220The text was updated successfully, but these errors were encountered: