Glossary / Code & Repos

Branch

A separate line of work where changes can happen before they touch the main version.

Updated July 2, 2026

A branch is a separate line of work inside git: a place to experiment, fix, or build without touching the version everyone relies on. The main version stays stable until your work is ready. When an agent works on code, it often creates a branch with a clear name like fix-search-filter, makes commits as the work progresses, and opens a pull request when it’s ready for review.

A shared client proposal is the everyday version. There’s a final version the team trusts. Before you rewrite a section, you make a draft copy. You can edit it, ask someone to review it, and compare it back to the final, while the trusted proposal stays untouched.

Why you care

A branch is a draft space. It lets you ask an agent to work without treating every change as final, which makes review calmer: inspect the difference, test the result, ask for revisions, then merge. If two branches change the same part of the same file, you get a merge conflict, which is just Git asking a person to decide the final version. Good work needs a place to be unfinished before it becomes official.