Code review

How it works

Every branch has a diff view comparing it to the default branch. Open it from the repo page — click the branch name to see what changed.

The diff shows file-by-file changes. Click any line to leave a comment. Comments are visible to everyone with access to the repo. Delete your own comments when they're resolved.

Why no pull requests

Pull requests are an artifact of fork-based open source workflows. In a team that owns its repos, they add ceremony without adding safety. gittan uses gated branches instead — the pipeline decides if a push is accepted, not a manual approval step.

Code review still matters. But it happens on the branch diff, not on a PR form. Comments are tied to the branch and the code — not to a merge request lifecycle.

Where to find it

Navigate to a repo, then pick a branch from the branch list. The diff view opens with all changed files collapsed. Expand a file to see its patch, and click a line number to comment.

Scope

Comments are scoped to a branch. When the branch is merged or deleted, its comments go with it. There is no cross-branch comment thread — each branch is its own review context.