Essential Git for Scientists
  • Introduction
  • Basic Concepts
    • Version Control
    • Git
    • Repo
    • Commits
    • Branches
    • Remotes
    • GitHub
    • De-centralisation
    • Summary
  • Basic Operations
    • Install Git
    • Create a Repo
    • Make a Commit
    • Inspect a Previous Commit
    • Revert a Change
    • Make a Branch
    • Extend a Branch
    • Fast-forward merge
    • Resolve conflicts
  • Intermediate Concepts
    • Commits
    • Three Trees
    • Rebase
    • Fetch
    • Pull
    • Push
  • Advanced Concepts
    • Reset
    • Interactive rebase
    • Formatted patches
    • Blame
    • Stash
    • Log filter
  • Cookbook
    • Undo
    • Branches
    • Diff
    • Stash
    • Merge
    • Hooks
    • Squashing
    • Rebase
    • Interactive Rebase
    • LFS
    • Submodules
    • Remote
    • Force push
    • Identify merged branches
    • Formated patches
    • Apply patches
    • Interactive rebase
    • Squash commits
    • Pull rebase
    • Log
    • Blame
    • Biset
    • Reset
  • Exercise
    • Exercise 1
    • Exercise 2
Powered by GitBook
On this page
  1. Basic Concepts

Remotes

A repo can be local (on your own computer) or remote (on a server). For example, a repo on your D drive work directory is local, while a repo on your GitHub is a remote.

Remotes are mainly used for collaborating with other contributors. This can be in a team environment where changes from colleagues are constantly exchanged. Or it can be for open source projects, where anyone from the public can be a contributor.

Locals can get data (fetch or pull) from or send data (push) to the remotes. Data can be transferred using SSH, HTTPS or the GIT protocol.

Pull and fetch are similar operations, but quite confusing for beginners. More on that later. So far, just know they are used to downlink data from remotes.

Branches are the mian players when working with remotes. E.g. when we pull or push, data are sent and received by specific branches.

PreviousBranchesNextGitHub

Last updated 1 year ago