Knowledge/Domain
Getting changes from a working copy into the world.
21 notes, plus everything one link away
Drag to pan · hold ⌘/ctrl and scroll — or pinch — to zoom.
Most connected first
Automatically building and testing every change, so integration problems surface immediately.
Version Control & Delivery·17 connections
A second person reading a change before it lands, and the practices that make it worth the time.
Version Control & Delivery·15 connections
A proposal to merge a branch, carrying review, automated checks, and the discussion around it.
Version Control & Delivery·13 connections
A system recording the history of a project's files, enabling branching, merging, and recovery.
Two changes that merge cleanly and are incompatible in meaning.
Version Control & Delivery·12 connections
Everyone integrating into one shared branch continuously, with short-lived feature branches.
The convention governing what branches exist, what they mean, and how work reaches production.
Version Control & Delivery·11 connections
Combining two lines of work by comparing both against their common ancestor.
A lightweight convention giving commit messages a machine-readable type and scope.
Version Control & Delivery·10 connections
An additional working directory attached to one repository, each on its own branch.
Replaying a branch's commits onto a new base, producing new commits with the same changes.
Collapsing a branch's commits into one before merging, trading granularity for a clean main history.
A commit containing exactly one logical change, complete and independently sound.
Version Control & Delivery·9 connections
A recorded snapshot of a project with a message explaining it.
Automatically releasing every change that passes validation.
Validating changes against the state they will actually merge into, in order, rather than in isolation.
A version-numbering convention where the number communicates the kind of change.
A chain of dependent changes, each reviewed separately and merged in order.
Protecting against compromise arriving through the code and tooling a project depends on.
A generated file recording the exact dependency versions an install resolved to.
Version Control & Delivery·8 connections
Overlapping changes that a merge cannot combine automatically, requiring a decision.