Obtain a copy of the model (using git)

First: Visit this page: https://git-scm.com/book/en/v2/Getting-Started-First-Time-Git-Setup

Then use the command

git clone git@github.com:metno/noresm.git

If you get error messages, verify that you can open the page https://github.com/metno/noresm in a web-browser. If you can not, you are probably not a github-user or not member of the noresm group on github. Send email to alf.grini@met.no (with a copy to trond.iversen@met.no) to get the right permissions. You can create the github user yourself. Go to https://github.com/join and create a user. Make user-name which is easy to understand, for example FirstnameLastname. You can attach several email-addresses to the same user.

To make life easier and avoid typing passwords all the time, follow the recipe here: https://help.github.com/articles/generating-ssh-keys/

Verify that you have the correct checkout

When you have cloned the model, check that you have gotten what you wanted!

Check that your favourite branch is available using the command

git branch --all

To check out (locally) your favourite branch and to start working on it, write

git checkout -b myBranchName origin/myBranchName

(Note that myBranchName must be one of the branches listed by the above command)

If you don't user the “-b” option, you will get something which is not correct. Make sure you are tracking a remote branch. You can write

git branch -vv

to see which remote branch you are tracking.

Note that once a branch has been checked out using the -b option, you can switch between any of your checked out branches using the command

git checkout aCheckedOutBranchName

Modify files

Modify the code (for example a file named myChangedFile.F90) and send back to your local repository through

git add myCHangedFile.F90

git commit -m "aMessage"

Verify, using the tool “gitk” that the changes make sense.

Send modifications from github

git pull

To be absolutely sure about branch names etc, you can do

git pull remoteName remoteBranchName:myLocalBranchName

which if your are changing the master-branch would translate to

git pull origin master:master

Send modifications to github

This command assumes that your changes go to the remote branch named like your branch (which is most of the times the case)

git push

You can also do (to be completely sure):

git push remoteName myLocalBranchName:remoteBranchName

which if your are changing the master-branch would translate to

git push origin master:master

(The above command means push my changes to the remote named “origin” from my local branch named master to the remote branch named master. If you are changing another branch than master, you must obviously not write “master”.

If you don't understand and want to get back to svn

http://www.git-tower.com/blog/git-for-subversion-users-cheat-sheet/