Branches

Branches on Pierre are supercharged collaborative surfaces for folks to present their changes, discuss ideas, review code, and so much more.

Once you have at least one repository setup and pushed to Pierre, you can start to work with branches. On Pierre, there are no merge requests or pull requests—branch pages are created automatically as soon as you push to our Git server. Create a Git branch, make your changes, push it up, and watch Pierre’s automated and AI-powered branch features go to work for you.

Pushing Branches

To push a branch to Pierre, you need to have a repository setup and pushed to Pierre. If you haven’t done that yet, check out the Repositories section.

# Assuming you have `origin` set to Pierre’s Git server
git push origin {branch}

With a successful push, you’ll see the following in your terminal:

➜ ~/my-project/ (feature-branch) git push origin feature-branch
Total 0 (delta 0), reused 0 (delta 0), pack-reused 0
remote:
remote:
remote: View this branch at:
remote: https://pierre.co/{workspace}/{repo}/feature-branch
remote:
remote:
To git.pierre.co:/repos/{workspace}/{repo}.git
 * [new branch]          head -> feature-branch

There’s a handy shortcut link to your new branch in the output. Click it to view your newly created branch page on Pierre.

Viewing Branches

Once your branch has been pushed to Pierre, you’ll find it on your Your work > Changes page (as well as on the repository page).

AI Summary & Highlights

Viewing the branch, you’ll see an AI-powered summary at the top, followed by three notable highlights, and then the branch’s diff.

The notable highlights are generated by AI to help you quickly understand the branch’s content, even without a branch description from the authors. As additional changes come in, the highlights will update to reflect them.

AI Categories

Pierre automatically categorizes the type of work that is happening on every change surface.

These categories are based on the diff itself and can help you quickly understand what’s changed. Click a category to filter the diff to that specific type of change.

Categories are fully generative, and range from things like "UI-components" and "API endpoints", to "documentation copy" and more.