---
title: Use branches for team development
description: Keep feature work separate from the main branch and merge it after testing and peer review.
---

import WorkshopRecordingLink from '../../../../components/workshops/WorkshopRecordingLink.astro';

[Git and GitHub Workshop: CryptX 2.0](https://www.youtube.com/watch?v=fRzFBDPsmEI)

<WorkshopRecordingLink href="https://youtu.be/fRzFBDPsmEI" />

## Keep the main branch stable

In a professional team, developers do not make feature changes directly on the main production branch. They create a separate branch for a piece of work, which lets the main line stay stable while that change is developed. [The workshop introduces this team practice](https://youtu.be/fRzFBDPsmEI?t=5039).

## Test and review before merging

When the work is ready, the team tests it and asks peers to review the change. The branch is merged into the main branch only after that process. Pull requests provide a shared place for this review and discussion before the merge.

[Continue to student resources](/docs/si/workshops/git-and-github/developer-pack-and-certificate)