branching strategy

A team's agreed rules for which branches exist, how long they live and how work moves between them.

In more detail

Git Flow and trunk-based development are the two best-known. The right one depends on how you deliver: software released as numbered versions benefits from release branches, while continuously delivered web applications do better with one trunk and short-lived branches.

Related terms

Taught in

References