Pull Request

A short document recording one significant technical decision, its context, and its consequences, kept alongside the code so later readers know why the system is shaped the way it is.

A commit containing exactly one logical change, complete and independently sound.

Bots that open pull requests whenever a dependency releases a new version, how they keep upgrades small and security patches fast, and how they turn into noise or a supply-chain risk when misconfigured.

Server-side rules that stop people from pushing straight to important branches, requiring reviews, passing checks, and intact history instead.

The convention governing what branches exist, what they mean, and how work reaches production.

A curated, human-readable record of the notable changes in each version of a project, written for the people who use it rather than the people who built it.

A second person reading a change before it lands, and the practices that make it worth the time.

A lightweight convention giving commit messages a machine-readable type and scope.

Systems tend to reproduce the communication structure of the organization that built them.

The two basic ways Git joins branches, by sliding a branch pointer forward or by recording a new commit with two parents, and how the choice shapes a project's history.

A branch created to develop one change in isolation before merging it back, a workflow that keeps the main line stable but grows riskier the longer the branch lives, since its divergence from everyone else's work compounds.

Overwriting a remote branch with local history that doesn't contain it, the operation that makes rewritten history shareable and silently deletes other people's work when used carelessly.

Showing, for every line of a file, the commit and author that last changed it, the starting point for finding out why code is the way it is.

Git's shelf for uncommitted work, which clears the working tree so you can switch tasks, and the reasons a throwaway commit or a second worktree is often the better shelf.

Using a Git repository as the live source of truth for deployed state, reconciled continuously by an in-cluster agent.

Requiring a person's judgment at chosen points in an otherwise automated process.

The time spent debating an item is inversely proportional to its actual stakes.

Validating changes against the state they will actually merge into, in order, rather than in isolation.

Two changes that merge cleanly and are incompatible in meaning.

Collapsing a branch's commits into one before merging, trading granularity for a clean main history.

A chain of dependent changes, each reviewed separately and merged in order.

Everyone integrating into one shared branch continuously, with short-lived feature branches.

A system recording the history of a project's files, enabling branching, merging, and recovery.