{"id":1600,"date":"2018-12-13T16:45:56","date_gmt":"2018-12-13T16:45:56","guid":{"rendered":"http:\/\/ri.itservices.manchester.ac.uk\/csf3\/?page_id=1600"},"modified":"2026-02-12T15:32:11","modified_gmt":"2026-02-12T15:32:11","slug":"git","status":"publish","type":"page","link":"https:\/\/ri.itservices.manchester.ac.uk\/csf3\/software\/tools\/git\/","title":{"rendered":"git & git-lfs"},"content":{"rendered":"

Overview<\/h2>\n

Git is a version control system, which allows you to keep old versions of files and directories (usually source code), keep a log of who, when, and why changes occurred, etc.,<\/p>\n

From October 2025, version 2.47.3 is the system-wide default (if you load no modulefile.) Hence it is no longer necessary to load a modulefile, unless you specifically need an older version! <\/p>\n

git-lfs<\/a> Git Large File Storage (LFS) replaces large files such as audio samples, videos, datasets, and graphics with text pointers inside Git, while storing the file contents on a remote server like GitHub.com or GitHub Enterprise. As of December 2025, Git-LFS version 3.6.1 is the system wide default, so a module does not need to be loaded.<\/p>\n

If you require a different version to the one installed we advise that you install it in your home directory.<\/p>\n

Restrictions on use<\/h2>\n

All users of the system can access the software.<\/p>\n

Set up procedure<\/h2>\n
\nNote that long-time users of the CSF may need to edit your ~\/.gitconfig<\/code> or ~\/.ssh\/config<\/code> files to remove old, proxy-related config (see below.)\n<\/div>\n

We recommend using the newer, system-wide version of git by NOT loading any modulefiles. This gives you immediate access to version 2.43.5 (note – if we install newer versions of git, we will revert back to providing them via modulefiles.)<\/p>\n

\r\n# No modulefile loaded\r\nyou have access to git 2.47.3<\/em>\r\nyou have access to git-lfs 3.6.1<\/em>\r\n\r\n# Or load one of the following modulefiles\r\nmodule load tools\/gcc\/git\/2.43.0\r\nmodule load tools\/gcc\/git\/2.24.0\r\n<\/pre>\n
To use git-lfs use:<\/p>\n
\r\nmodule load tools\/bintools\/git-lfs\/2.8.0\r\n<\/pre>\n
Running the application<\/h2>\n
Don’t clone into scratch<\/h3>\n
We strongly recommend that you clone repositories into your home area<\/em>, or other research data storage, NOT your scratch area.<\/p>\n
This is because the scratch clean-up policy can automatically delete files not accessed for at least 3 months. A cloned repository often contains many files that you might not access and so the scratch clean up could remove files without you being aware of it.<\/p>\n
Usage<\/h3>\n
On the command line type git<\/code>.<\/p>\n
If you wish to prepare a repository for use with git-lfs run the following inside each repository:<\/p>\n
\r\ngit lfs install\r\n<\/pre>\n
External Access using https:\/\/<\/h3>\n
You can run your commands directly on the login node, or on a compute node (via srun<\/code>), or in a batch job. For example:<\/p>\n
From the login node or in a jobscript:<\/p>\n
\r\ngit clone https:\/\/github.com\/myproject.git\r\n<\/pre>\n
Or, from an interactive session on a compute node:<\/p>\n
\r\n# On the login node, request an interactive session\r\nsrun -p interactive -t 0-1 --pty bash\r\n  #\r\n  # Wait until you are logged in to a compute node\r\n\r\n# Now run your commands as normal\r\ngit clone https:\/\/github.com\/myproject.git\r\n<\/pre>\n
Note: If you get an error about the web-proxy, please edit your ~\/.gitconfig<\/code> file:<\/p>\n
\r\ngedit ~\/.gitconfig\r\n  #\r\n  # Remove 'proxy' line from the [http] section\r\n  [http]\r\n  proxy = http:\/\/some.proxy.addr<\/em>:3128\/       # REMOVE THIS LINE FROM YOUR ~\/.gitconfig FILE<\/strong>\r\n<\/pre>\n
Note:<\/strong> You may also need to remove some old config from your ~\/.ssh\/config<\/code> file if using the ssh:\/\/<\/code> protocol (see below<\/a>)<\/p>\n
Once cloned, you may wish to work with a specific tag:<\/p>\n
\r\n# List all tags (and those matching a pattern)\r\ngit tag\r\ngit tag --list v2*\r\n\r\n# Work with a specific tag\r\ngit checkout tagname<\/em>\r\n\r\n# Display which tag you're on\r\ngit describe --exact-match --tags\r\n<\/pre>\n
External Access to github.com using https:\/\/ (with Personal Access Tokens)<\/h3>\n
Github are moving away from using https:\/\/<\/code> with passwords to access your repos. Their blog post<\/a> says:<\/p>\n
If you are using a password to authenticate Git operations with GitHub.com today, you must begin using a personal access token over HTTPS or SSH key by August 13, 2021, to avoid disruption.\n<\/p><\/blockquote>\n
See their documentation on how to create a Personal Access Token<\/a> (this is similar to a random, expiring password.) <\/p>\n
External Access to github.com using ssh:\/\/ (with key)<\/h3>\n
An alternative to using Personal Access Tokens with https:\/\/<\/code> is to set up a public-private key-pair for your github.com account, which will give you password-less access to github.com via ssh:\/\/<\/code>.<\/p>\n
The following is a quick summary of how to setup ssh:\/\/<\/code> access to github on the CSF using a key-pair:<\/p>\n
\r\n# If not already done so, create a key-pair on the CSF:\r\nssh-keygen -t ed25519 -C your.email@manchester.ac.uk.com -f ~\/.ssh\/id_github\r\n  #\r\n  # We recommend protecting your key with a passphrase when asked, but this is optional.\r\n  # If you intend to run git from batch jobs, do not set a passphrase.\r\n\r\n# Now edit your ~\/.ssh\/config file and add the following:\r\ngedit ~\/.ssh\/config\r\n\r\n# ADD<\/strong> the following config to make ssh:\/\/ use your key\r\nHost github.com\r\n  IdentityFile ~\/.ssh\/id_github\r\n  IdentitiesOnly yes\r\n\r\n  # REMOVE<\/strong> any old config if present\r\n  # HostName nataas.itservices.manchester.ac.uk\r\n  # IdentityFile \/mnt\/iusers01\/support\/mbexegc2\/.ssh\/id_ed25519\r\n  # StrictHostKeyChecking  no\r\n  # Port 2022\r\n\r\n(save the file)\r\n\r\n# Now look at the public key-file contents (we'll need the displayed line shortly):\r\ncat .ssh\/id_github.pub\r\nssh-ed25519 AAA................... your.email@manchester.ac.uk\r\n<\/pre>\n
Now login to your github.com<\/a> account as normal.<\/p>\n
    \n
  1. Then go to your Account Settings<\/code><\/li>\n
  2. Then SSH and GPG Keys<\/code>.<\/li>\n
  3. Press the New SSH Key<\/code> green button and paste in the above line.<\/li>\n<\/ol>\n
    Finally, test you connection from the CSF:<\/p>\n
    \r\n# On the CSF login node:\r\n# Use the github test method to check your keys\r\nssh -T git@github.com\r\n  # If you saved your key with a passphrase you'll be prompted to enter it\r\n# You should see\r\nHi githubusername<\/em>! You've successfully authenticated, but GitHub does not provide shell access.\r\n\r\n# Return to the login node\r\nexit\r\n<\/pre>\n
    VSCode and github.com<\/h2>\n
    Some VSCode extensions will attempt to contact github.com from the CSF login node. This occurs when you have VSCode installed on your<\/em> local PC\/laptop, and you use the “SSH Extension” in VSCode to login to the CSF and edit code in your CSF home directory. But it is not<\/em> possible to make VSCode run the git commands on a CSF compute node, as is normally required.<\/p>\n
    To allow VSCode to work with github.com, some access to github from the login node will now work. We have added github.com to the “allow-list” of sites that can be contacted from the login node. Please note that the Research Infrastructure team DO NOT manage the list of permitted sites that can be contacted from the CSF login nodes. We can only make a request that access be granted to certain sites. <\/p>\n
    If your use of VSCode is trying to contact a github service from the CSF login node and is being blocked, please contact us with the domain name (e.g., something<\/em>.github.com) that is reported in any error message you receive. <\/p>\n
    Further info<\/h2>\n