# Open and review change requests

Propose a branch for merging, from the terminal or the web, and review it line by line.

A change request is Lorx's pull request: a branch proposed for merging into another. Each push to the branch adds a revision, and the changes are always shown against where the branch left its base (as `git diff base...head` shows them).

## Open one

Push a branch, then open the change request from the web, or from your terminal:

```sh
git switch -c fix-login
# …commit…
bit cr create
```

`bit cr create` pushes the branch first if the remote's copy is missing or behind.
- Its title and description come from the branch's commit when there is exactly one; with several, your editor opens.
- `-t` sets the title, `-b` the description (or `-F file`, or `-F -` for stdin).
- `--base` sets the branch to merge into.
- `--draft` opens it as a draft.

## Find and read them

```sh
bit cr list                # open ones (drafts included)
bit cr list -s merged -A anna
bit cr view 42             # state, branches, whether it merges cleanly, revisions, timeline
bit cr diff 42             # the changes as a diff (--name-only for just the files)
bit cr checkout 42         # the head branch, locally
```

`--json` on `list` and `view` prints the API's JSON, for scripts and agents.

## Review

On the web, open the change request's **Files** tab and comment on any line. Replies stay in the comment's thread, and you resolve the thread when it's settled. When you've been through the change, approve it or ask for changes.

## Drafts

A draft can't merge until it is marked ready: `bit cr ready 42` (or `--undo` to make it a draft again).