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
3: checkout the master branch and sync everywhere:
41
-
**git checkout master**
42
-
**git pull upstream master**
43
-
**git push origin master**
44
-
45
-
4: Make a new branch (name it something appropriate, here assuming a bugfix) and make edits on this branch:
46
-
**git checkout -b bugfix**
47
-
48
-
5: When edits are done, do all **git add**s and **git commit**. In the commit, make a succinct (<70 char) summary, followed by a blank line and a longer description. Reference any outstanding issues addressed using the syntax **#ISSUE_NUMBER <#>**.
49
-
50
-
6: Push the edited branch to the origin remote (i.e. your fork) on github:
51
-
**git push -u origin bugfix**
52
-
53
-
7. On github, go to your fork and hot the pull request (PR) button, and wait for the MITgcm head developers to review your proposed changes.
54
-
You may get additional questions or requests before your changes are accepted into the primary MITgcm source code.
55
-
56
-
57
-
Detailed Guide for those less familiar with Git and Github
What is Git? Git is the version control system used to maintain the MITgcm, coordinating work among the many model contributors, and tracking changes in model code.
61
-
If you are familiar with the older form of version control used by the MITgcm (CVS), there are many similarities, but we now take advantage of the modern capabilities offered by Git.
62
-
63
33
You will need a GitHub account, but that's pretty much it!
64
34
65
35
1: Fork the project and create a local clone (copy)
0 commit comments