in πŸ““ Notes


Git is a distributed version control system for tracking changes in source code during software development.

  participant W as Workspace
  participant S as Staging
  participant LR as Local Repository
  participant R as Remote
  W->>S: git add/mv/rm
  S->>LR: git commit
  W->>LR: git commit -a
  S->>W: git reset <file>
  LR->>R: git push
  LR->>W: git reset <commit>
  R->>LR: git fetch
  W->S: git diff
  W->LR: git diff HEAD
  R->>W: git clone/pull

How it works

  • Immutable objects represent files (blob), directories (tree) and changes (commit).
  • Content-addresses by cryptographic hashes.
  • Forms a Merkle DAG.
  • Most metadata is just references. Hence, inexpensive to update or create.
  • Version changes only update references or add objects.
  • Version changes to other users is just transferring objects and updating remote references.


# Stage all
$ git add -A

# Add specific files
$ git add paths...

# Remove specific files
$ git rm paths...


More on git branching.


# Create a new branch
$ git branch <branch-name>

# Checkout the new branch
$ git checkout <branch-name>

# Create and checkout a new branch
$ git checkout -b <branch-name>


More on branch merging.

# Checkout master
$ git checkout master

# Merge hotfix into master
$ git merge hotfix


$ git branch -d <branch-name>


We can reset a file to another commit via:

$ git reset <commit> <file...>
  • By default, the command just unstages the files.
  • By omitting the file, the entire repository will be reverted.
  • By adding the flag --hard, the entire repository reverts to the specified commit.

Revert (reflog)

Git keeps a log of all ref updates (checkout, reset, commits, merges, etc). It can be viewed with:

$ git reflog

# Ref log for specific branches
$ git reflog show <branch>

# Revert last `git reset`
$ git reset '[email protected]{1}'

Or if you don't know what a response is, you can always write a webmention comment (you don't need to know what that is).