Kamus AI
Branch
A separate line of work in a repository: its changes do not touch the main version until merged.
A branch separates unfinished work from the main branch. Every feature, fix or agent experiment should get its own branch, so its diff can be reviewed as a whole and thrown away if it fails. The main branch is protected: only code that passed its tests and its review gets in, through a merge.
Also called: Branch, main branch, main
Related terms
Appears in 15 lessons
- One task, one worktree, commits with explicit paths
- One feature from plan to review
- A release with a rehearsal and a way back
- Git and branches
- Worktrees and parallel work
- Session 3: build with tests and a separate reviewer
- Session 4: release with a runbook and a rollback drill
- Session 6: demo, handover and what next
- A workspace where an agent may be wrong
- Project instructions and first permissions
- Project: a team instruction file and permission rules
- Stop conditions
- Project: a programme with a ledger
- Permissions as narrow as the task
- A human gate before release