Berrit workflow

Change request

Berrit calls a request to review code a change. It follows one commit through revisions with a stable number, link and conversation.

Change #142

Rev 1 · approved

1cb03ba

Rev 2 · rebased

9079bc1
Approval carried over
New commit hash. Same change link and approval.

Send a revision as you address feedback

Amend the commit and send it again. Reviewers can compare the submitted revisions on the same change page.

Publish comments and a vote together

Publish inline drafts with a message or vote. Repository rules can require approval from specific people or teams based on changed paths.

Keep approval when the patch stays the same

An unchanged patch keeps its approval through a rebase. For an edit, the repository decides whether approval still counts. Berrit asks prior approvers to look again.

Open your first change.

Get started