CUCC Expedition Handbook - Git Quick

Quick Reminder - Git

Version Control Software Reminders

git content model

This is NOT a tutorial. This is a set of reminders for people who already know all this stuff.

Since 2019 all use of version control software requires that you have key-pair setup already set up before any of this will work on your own machine.

- check that you can get ssh working before trying to run git too

If you can get to the expo laptop try these commands on that first as the key exchange has already been done. If the key exchnage has not been done then none of this will work.

Open a terminal in a new directory, e.g. /tmp/experiments/ in which you want to create the repo. It will automatically create a folder with the repo name e.g.'troggle' in that directory.

expoweb (The data management system)
git clone ssh:// (read/write)
troggle (The data management system backend)
git clone ssh:// (read/write)
loser (The survey data) - this will fail until it is moved from hg to git
git clone ssh:// (read/write)
git clone ssh:// (read/write)

Using git

git bread & butter commands subsetYou may find these useful:

Using git in Windows

Do not use the official "git for Windows" client software as it doesn't understand symlinks in the WSL filesystem we use on Windows. Use VS Code which understand WSL or a command line git in a WSL terminal window.

"Git is a 4 handle, dual boiler espresso machine – when all you need is instant."

Once you've downloaded and installed a git client, the first step is to create what is called a checkout of the data management system. This creates a copy on your machine which you can edit to your heart's content. The command to initially check out ('clone') the entire expo data management system is:

git clone ssh://

for subsequent updates

git update

will generally do the trick.

After you've made a change, commit it to you local copy with:

git commit (you can specify filenames to be specific)

The first time you do this on a Windows machine it will probably not work as it does not recognise the server key exchange. Fix this by running putty (downloading it from, and connecting to the server '' (on port 22). Confirm that this is the right server. If you succeed in getting a shell prompt then ssh connection are working and git should be able to clone the repo, and send changes back.