Prasanta Kumar Behera
Git for Engineers — Level by Level
Learning Hub / CI/CD & GitOps

Git for Engineers — Level by Level

Beginner → Advanced8 lessonsAvailable

Every pipeline, every GitOps deployment and every infrastructure change starts with a Git commit. Learn how Git really stores your work, the daily workflow, branching and merging, collaborating through pull requests, choosing a branching strategy, undoing almost any mistake, and running repositories safely for infrastructure and GitOps.

You'll meetgitcommitbranchmergerebasepull requesttrunk-basedtagsresetrevertreflogbisectpre-commitCODEOWNERSsigned commits
Start lesson 01 →

What you'll be able to do

  • Explain what a commit, a branch and a remote really are
  • Work confidently every day: stage, commit, branch, merge, rebase and resolve conflicts
  • Collaborate through pull requests with protected branches and reviews
  • Pick a branching and release strategy that fits the team
  • Recover from mistakes with restore, reset, revert, reflog and bisect
  • Run repositories safely for infrastructure-as-code and GitOps

Before you start

Linux command line (Linux — Level by Level, Level 1).

How it works

Each lesson: plain-language idea → how it really works → hands-on. Each section ends with a cheat sheet & self-check.

Curriculum

Lessons marked “Read” are ready; the rest are on the way.

Level 1 — Foundations

  1. 01How Git worksSnapshots, commits, trees and refs: the model behind every commandRead →
  2. 02The everyday workflowStatus, add, commit, diff, log, .gitignore and good commit messagesRead →
  3. 03Branching and mergingBranches, fast-forward and merge commits, rebase, resolving conflictsRead →
  4. 📋Cheat sheet & self-checkEvery command from this section on one page, then 10 questions to check yourself.Open →

Level 2 — Working in a team

  1. 04Remotes and pull requestsClone, fetch, pull, push, forks, pull requests, protected branches and reviewsRead →
  2. 05Branching strategies and releasesTrunk-based, GitHub flow, GitFlow, release branches, tags and semantic versioningRead →
  3. 06Undo and recoveryRestore, reset, revert, stash, cherry-pick, reflog and bisectRead →
  4. 📋Cheat sheet & self-checkEvery command from this section on one page, then 9 questions to check yourself.Open →

Level 3 — Git for platforms

  1. 07Repositories for infrastructure and GitOpsMono vs poly repo, CODEOWNERS, pre-commit hooks, signed commits, keeping secrets outRead →
  2. 08Large repos and troubleshootingShallow and sparse clones, LFS, submodules vs subtrees, and fixing common errorsRead →
  3. 📋Cheat sheet & self-checkEvery command from this section on one page, then 6 questions to check yourself.Open →

Real-world scenarios

Work through each one: symptom → misleading signal → evidence → root cause → prevention.

A secret was pushed to the main branch

Contain it, rotate it, then decide whether to rewrite history.

The release branch and main have drifted apart

Get fixes into both without losing or duplicating changes.

Someone force-pushed over a teammate's work

Find the lost commits with reflog and protect the branch.

This site is a public version of my personal engineering knowledge hub. It intentionally excludes confidential company information and internal operational details.