Git
Studies in this cluster, in series order. Each one keeps its own URL.
DevOps
Kubernetes workloads, CI/CD pipelines, artifact digests, supply-chain controls, Git rebase, merge, and recovery, and Terraform state, modules, and safe change you can defend in interviews.
Git
6 studies- 1.Git — Everyday Commands, Rebase vs Merge & Safe HistoryGit is a content-addressed DAG of commits plus movable refs and a staging index. This hub is the decision matrix for rebase, merge, and squash, and the map to objects, history surgery, recovery, and pull-request hygiene.
- 2.Git Objects, Refs, Index & Working Tree — Mental ModelEverything in Git is an immutable content-addressed object or a mutable ref. The index is the staging area between the working tree and the next commit. Rebase, reset, and reflog stop feeling like magic once those three trees are obvious.
- 3.Rebase vs Merge vs Squash — When, Why & TradeoffsMerge records parallel work with a join commit. Rebase replays commits onto a new base and mints new ids. Squash collapses a branch into one commit. The wrong choice on a shared branch hurts the team. The wrong choice on a private branch mostly wastes review time.
- 4.History Surgery — Amend, Interactive Rebase, Fixup & AutosquashHistory surgery cleans private commits before review. Amend fixes the tip. Interactive rebase reorders, squashes, rewords, or edits. Fixup and autosquash fold review follow-ups into the commit they belong to. Every one of these tools mints new commit ids.
- 5.Cherry-pick, Revert, Reset & Reflog RecoveryCherry-pick copies one commit's changes onto another branch as a new commit. Revert adds an inverse commit. Reset moves a branch pointer. Reflog is the local record of where HEAD used to point, and it is how you get a commit back after a bad rebase or reset.
- 6.Branching, PR Hygiene, Bisect, Worktrees & HooksDay-to-day collaboration is branching policy, pull-request hygiene, bisect, worktrees, and hooks. Trunk-based development keeps main releasable with short branches. Bisect is a binary search over commits. Worktrees are extra checkouts on one object database.