Knowledge/Domain
Getting changes from a working copy into the world.
Drag to pan · hold ⌘/ctrl and scroll — or pinch — to zoom.
A second person reading a change before it lands, and the practices that make it worth the time.
Version Control & Delivery·25 connections
Automatically building and testing every change, so integration problems surface immediately.
Version Control & Delivery·20 connections
A system recording the history of a project's files, enabling branching, merging, and recovery.
Version Control & Delivery·19 connections
A proposal to merge a branch, carrying review, automated checks, and the discussion around it.
Version Control & Delivery·16 connections
Automatically releasing every change that passes validation.
Version Control & Delivery·15 connections
A version-numbering convention where the number communicates the kind of change.
Version Control & Delivery·14 connections
Protecting against compromise arriving through the code and tooling a project depends on.
Version Control & Delivery·13 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·12 connections
The number of people who would have to leave before a project stalls.
Two changes that merge cleanly and are incompatible in meaning.
Combining two lines of work by comparing both against their common ancestor.
Version Control & Delivery·11 connections
A lightweight convention giving commit messages a machine-readable type and scope.
Version Control & Delivery·10 connections
Systems tend to reproduce the communication structure of the organization that built them.
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.
With enough users, every observable behavior of an interface becomes a dependency for somebody.
A generated file recording the exact dependency versions an install resolved to.
Validating changes against the state they will actually merge into, in order, rather than in isolation.
A license family that imposes little beyond attribution and a warranty disclaimer.
A chain of dependent changes, each reviewed separately and merged in order.
A licensing strategy that uses copyright to require derivative works to stay open.
Version Control & Delivery·8 connections
Overlapping changes that a merge cannot combine automatically, requiring a decision.
Reverting a running system to a previous known-good version, as distinct from fixing forward.
Deploying a new version while the service keeps serving every request, with no maintenance window.
Running two identical production environments and switching traffic between them instead of upgrading one in place.
Version Control & Delivery·7 connections
Shipping a change to a small slice of traffic first, and only widening it once that slice looks healthy.
Using a Git repository as the live source of truth for deployed state, reconciled continuously by an in-cluster agent.
Version Control & Delivery·6 connections
Replacing servers wholesale on every change instead of patching them in place.
Defining infrastructure in version-controlled files instead of configuring it by hand through a console.
Version Control & Delivery·5 connections