-
Notifications
You must be signed in to change notification settings - Fork 24
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
Move MET repository from the NCAR to DTCenter organization. #1462
Comments
On 8/18/20, I actually moved the MET repo from the NCAR to DTCenter organization through GitHub. Details listed below:
Did this for all my development repositories on musial6. Also updated the repos used by the NB on dakota in /d3/projects/MET/MET_regression for MET-develop and MET-master_v9.1. |
Updated from github.com/NCAR to github.com/dtcenter using the following commands:
|
…he master_v9.1 bugfix branch.
I forgot to make 2 additional changes:
|
…ub.io and rename METdb to METdatadb.
…github.io and rename METdb to METdatadb.
…push Sphix documentation generated from the master_v9.1 branch up to gh-pages.
Describe the Task
Move the MET repository from the NCAR organization to the DTCenter organization. The GitHub URL needs to be updated in many locations:
These changes should be made to both the develop and master_v9.1 branches.
After the documentation updates are complete, re-push the met-9.1 User's Guide to GitHub pages.
Time Estimate
2 hours.
Sub-Issues
Consider breaking the task down into sub-issues.
No sub-issues required.
Relevant Deadlines
None
Funding Source
Define the source of funding and account keys here or state NONE.
Define the Metadata
Assignee
Labels
Projects and Milestone
Define Related Issue(s)
Consider the impact to the other METplus components.
This change does not affect the other repositories, but similar changes will be required in those repos.
Task Checklist
See the METplus Workflow for details.
Branch name:
feature_<Issue Number>_<Description>
Pull request:
feature <Issue Number> <Description>
The text was updated successfully, but these errors were encountered: