Change Requests

A Change Request is a versioned proposal to transform a repository. It can come from a branch in the same repository or from a fork.

Create a Change Request

Open Changes, select New Change Request, then choose the source and target. Upstream records the source, target, actor, and initial version.

Versions

When the proposed source changes, Upstream adds a new version instead of overwriting the old review target. Comments can remain conversational, while approvals, reviews, diffs, and checks stay pinned to the version they evaluated.

Use the version picker on a Change Request to inspect earlier snapshots.

State

A Change Request may be draft, ready for review, open, merged, or closed. Closing does not delete its history, and an eligible request can be reopened.

Merge readiness

The server decides whether a Change Request can merge. It evaluates repository state, permissions, approvals, required checks, merge conflicts, and the current version. The browser never invents a second readiness decision.

Update branch

When available, Update branch brings the target branch into the proposal using the repository's canonical merge service.