Skip to main content
ANVISoftware Solutions

Git & GitHub

Beginner8-12 hours4 modules15 lessons

Version control explained properly: commits, branches, merges, rebases, conflicts, pull requests and automated checks.

Start the first lesson

Prerequisites

None. This course assumes no prior knowledge of the subject.

Technologies

About this course

Git is usually learned as a handful of memorised commands, which works until something unexpected happens and the commands stop making sense. This course teaches the model first — commits, branches and history as a structure — so the commands become predictable.

Conflicts get real attention rather than being treated as an emergency. A conflict is Git telling you two changes touched the same lines and asking which you meant, and that is a normal part of collaborating.

The course ends on team workflow: pull requests, review habits that are useful rather than performative, and automating checks so review can focus on design instead of formatting.

Course roadmap

All 15 lessons are written and available.

Module 01

Git Foundations

The model behind the commands: snapshots, history, and where your files actually are.

4/4 ready
  1. 01Why Version Control ExistsExplain the problems version control solves and what a commit actually records.11 min
  2. 02RepositoriesCreate or clone a repository and understand what is tracked.12 min
  3. 03CommitsRecord focused changes with messages that explain the reason.14 min
  4. 04The Staging AreaChoose exactly what goes into the next commit.14 min

Module 02

Branching and Combining Work

Work in parallel, then bring it back together and handle the overlaps.

4/4 ready
  1. 01BranchesCreate and switch branches to work on things independently.14 min
  2. 02MergingBring a branch back and understand what a merge commit records.14 min
  3. 03RebasingReplay commits onto a new base, and know when not to.16 min
  4. 04Resolving ConflictsRead a conflict and resolve it deliberately.15 min

Module 03

Working with Others

Remotes, pull requests, review, and getting out of trouble.

5/5 ready
  1. 01RemotesPush, pull and fetch, and explain the difference between the last two.15 min
  2. 02Pull RequestsPropose changes in a reviewable, well-described form.14 min
  3. 03Code ReviewGive and receive feedback that improves the change.15 min
  4. 04Stashing, Tagging and ReleasesSet work aside temporarily and mark released versions.14 min
  5. 05Undoing and RecoveringRecover from common mistakes, including work you thought was lost.18 min

Module 04

Automation and Hygiene

Let machines check the mechanical things so humans review the design.

2/2 ready
  1. 01.gitignoreKeep build output, dependencies and secrets out of the repository.14 min
  2. 02GitHub ActionsRun checks automatically on every push and pull request.16 min

On completion

What you should take away

  • A commit is a snapshot with a parent; history is those snapshots linked together
  • A branch is a moving pointer, which is why branching is cheap
  • Conflicts are information about overlapping changes, not failures
  • Pull requests are where design feedback belongs; formatting should be automated

Recommended next course

Docker & Containers

Package applications so they run identically everywhere: images, Dockerfiles, volumes, networks, Compose and production concerns.

Continue to Docker

Have a project worth talking through?

Tell us what you're building or what's slowing your current system down. We'll give you a direct read on scope and approach.

Start a ConversationExplore Our Services