1# Merge requests
2
3A merge request proposes a branch for a target (the default branch unless set).
4
5```sh
6ermite mr create myrepo --source feature --title "Add feature"
7ermite mr show myrepo 1 --diff
8ermite mr merge myrepo 1 --head <commit> [--mode fast-forward|squash|merge] [--delete-branch]
9```
10
11Naming an issue with `#N` links it, and `Fixes #N` closes it on merge: see [issues](issues.md#merge-request-links).
12
13`ermite mr create` and `ermite mr close` print a confirmation followed by the full
14merge request web URL on its own line. With `--json`, merge request objects
15(create, show, list, close and merge) include `url` alongside the other fields.
16
17## Merge modes
18
19| Mode | Result | Needs |
20|---|---|---|
21| `fast-forward` (default) | the target moves to the head, no commit | the target is an ancestor of the head |
22| `squash` | one new commit with the merged tree, the target tip as only parent | the branch merges without conflicts |
23| `merge` | a merge commit with two parents, the target tip and the head | the branch merges without conflicts |
24
25- The server never rebases. A branch behind its target merges with `squash` or `merge`, or is rebased and pushed again for a fast-forward.
26- The server checks the mode again when it merges, whatever the badge showed, and refuses with the reason (the target moved, a conflict with the paths).
27- The merge is also refused when the branch moved since the reviewed `--head`.
28- With `failing_checks_block` on (default), the merge is refused while a check of the head failed or is still running.
29- The merge answers as soon as the target has moved. `--delete-branch` then deletes the source branch right after, in the background (unless it is the default branch or another open request uses it); if the branch moved meanwhile, it is kept.
30- Every mode is allowed by default, including in repositories that had only `fast-forward` and `squash` before `merge` existed: those gain `merge`. Disable a mode per repository with `ermite repo edit <repo> --merge-modes fast-forward,squash` (list the modes to keep).
31- Scopes: `mr:write` to open and comment, `mr:review` to give a verdict, `mr:merge` to merge.
32
33## Signed commits
34
35Squash and merge commits are signed by ermite's own key. The key is generated automatically the first time the server starts, belongs to the server, and its committer identity is `ERMITE_COMMITTER_NAME` / `ERMITE_COMMITTER_EMAIL`. `ermite signing-key show` prints its fingerprint and the `allowed_signers` line; use it to verify locally, or register the public key on GitHub or Forgejo.
36
37```sh
38ermite signing-key show --allowed-signers > allowed_signers
39git -c gpg.format=ssh -c gpg.ssh.allowedSignersFile=allowed_signers verify-commit <commit>
40```
41
42The merge box of the web page and the output of `mr merge --mode squash|merge` repeat this with the fingerprint.
43
44## Auto-merge
45
46A merge request can merge by itself once its checks passed.
47
48- The repository setting `allow_auto_merge` is off by default: `ermite repo edit <repo> --allow-auto-merge` (`=false` to turn it off).
49- Enable it with `ermite mr merge <repo> <n> --head <commit> --auto --mode squash` (`--head` is required, as for a plain merge; a head that moved is refused with "branch moved"), or with **Merge when ready** in the web merge box. Its separate mode choice offers every repository-allowed mode, even while the head conflicts or is behind. Auto-merge keeps the source branch; the delete-source checkbox applies only to an immediate merge. It needs `mr:merge` and a server with CI. Re-enabling replaces the previous mode and enabler.
50- The server merges when CI has settled on the head with every run complete and at least one check passed. A failing or unfinished check always blocks, whatever `failing_checks_block` says. The mode must still be allowed.
51- The merge is made as the person who enabled it. Their token is checked at every evaluation, even while checks are pending, and again at merge time under the merge lock: it must still be valid and allow `mr:merge` on the repository and the target branch. A token that no longer qualifies cancels the auto-merge.
52- A pending auto-merge shows in `mr show` (`auto_merge`), in the web merge box and as `merge_request_auto_merge_enabled` in `ermite watch`. A merge request merged this way has `auto_merged` true.
53- A failing, unfinished or conflicting head waits with auto-merge still on. A re-run or a target fix can make it pass; pushing a new source head cancels the recorded intent (the reason names the new head).
54- A manual merge supersedes auto-merge and publishes `merge_request_merged` with `auto=false`, without a cancelled event. A manual close clears it and publishes `merge_request_closed` followed by `merge_request_auto_merge_cancelled` with reason `closed`.
55- Cancellation reasons are `cancelled by <author>`, `closed`, `auto-merge was turned off in the repository settings`, `the <mode> merge mode is no longer allowed`, `the source branch was deleted`, `the branch moved to <short-head>`, and `the principal that enabled auto-merge can no longer merge <target>`. If a change wins the merge lock after the evaluator's first read, the merge-time reason is instead `auto-merge is off in <repo>`, `the <mode> merge mode is not allowed in <repo>`, `the source branch "<source>" no longer exists`, or `branch moved, read again: "<source>" is at <head>, not <recorded-head>`. Other permanent merge-time preconditions report `!<n> is <state>`, `!<n> is a draft: mark it ready for review first`, `the target branch "<target>" no longer exists`, `nothing to merge, "<target>" already is at <head>`, or `nothing to merge, "<target>" already contains <head>`.
56- Cancel it with `ermite mr merge <repo> <n> --cancel-auto` or **Cancel auto-merge** in the web merge box.
57
58## Mergeability
59
60The server checks in the background whether each open request merges with its target, and again whenever the source or the target moves. `mr show` prints it; the web merge box shows it as a live badge; `ermite watch` reports each change.
61
62| State | Meaning | Modes possible |
63|---|---|---|
64| `checking` | no result yet for the current branches | none (wait) |
65| `up_to_date` | the target is an ancestor of the head | all |
66| `behind` | the head lacks `behind` commits of the target (`behind_capped`: at least 1000) but merges without conflicts | `squash`, `merge` |
67| `conflict` | the merge conflicts; up to 20 `conflict_paths` are listed (`conflict_paths_truncated` when there are more); no paths means no common history | none (rebase) |
68
69```sh
70ermite mr show myrepo 1
71# mergeability  behind by 2, merges without conflicts (squash or merge commit; fast-forward needs a rebase)
72```
73
74In `mr show --json`, `mergeability` holds `state`, `behind`, `behind_capped`, `conflict_paths`, `conflict_paths_truncated`, `target_id` and `head_id`; it is `null` unless the request is open. `ermite watch` prints `merge_request_mergeability` events when the state changes (not on every push):
75
76```text
772026-10-19T14:00:00Z  merge_request_mergeability  myrepo!1 mergeability: behind by 2
78```
79
80In the web merge box a mode that is not possible is disabled with its reason, and the Merge button too when no mode is possible. A merge the server refuses (target moved, conflict, branch moved) shows the page again with the reason in the box.
81
82## Large diffs on the web
83
84The merge request, commit and compare pages list every changed file. Generated files (lockfiles, `vendor/`, `node_modules/`, minified or generated code) and large files (over 2,000 changed lines) are collapsed: the header and the counts show, the lines do not. "load diff" fetches that one file in place, in full, and you can comment on its lines. Without scripts the link reloads the page with that file loaded. After the first 25 files of a merge request, the other files load as you scroll.
85
86A commit page reads the hunks of its first 300 files with the page; the other files are listed collapsed and load one at a time. A file that cannot be shown in the browser, over 8 MiB of text or over 50,000 changed lines when loaded alone, has no "load diff": the page links to its raw blob instead, and its lines take no comment.
87
88The API and `mr show --diff --json` keep their limits (300 files, 2,000 changed lines per file, 20,000 in total, 8 MiB). A file read without its hunks has `truncated` set and `omitted` giving the reason: `large`, `budget` (the earlier files used the limits) or `unavailable` (over 8 MiB of text, or a line over 64 KiB, even alone). Files past the 300th are not listed and `diff_truncated` is set.
89
90## Notes
91
92A note is the only review object. It is published as soon as it is written: there is no draft and no submit step.
93
94```sh
95ermite mr comment myrepo 1 -m "General remark"
96ermite mr comment myrepo 1 -m "Why?" --path main.go --line 10-14 --side new
97ermite mr comment myrepo 1 -m "Fixed in ^3" --reply 2
98ermite mr resolve myrepo 1 2
99ermite mr edit-comment myrepo 1 2 -m "New text"
100ermite mr delete-comment myrepo 1 2
101```
102
103- Notes are Markdown, up to 8000 characters, rendered without raw HTML. Quote with `> `.
104- `^N` in a note or a description links to note N of the same merge request. A reference to a missing note stays plain text.
105- A note is general, on one line, or on a range `A-B` of lines on one side (`old` or `new`) of the diff. The lines must be in the diff.
106- Threads have one level: a reply (`--reply <id>`) takes the anchor of its root and cannot carry a verdict. Resolving or reopening is done on the root and covers its replies.
107- Only the author edits or deletes a note. An edited note shows "edited". A deleted note loses its text; a deleted root with replies stays as "deleted note".
108
109## Verdicts
110
111A root note can carry a verdict: `--approve` or `--request-changes`. The text may then be empty. A verdict needs the `mr:review` scope (or the owner); `mr:write` comments but cannot give one.
112
113- A verdict ends a review: agents and `ermite watch` act on it, not on each note.
114- Verdicts are informative: none blocks or allows a merge.
115- `mr show` lists the latest verdict of each author (`verdicts` in `--json`).
116- An approval is stale once the branch head differs from the head it was given on. Changes requested stay current until their author gives a new verdict, whatever is pushed.
117- Verdicts are immutable: editing or deleting the note keeps its verdict. Only a new verdict of the same author replaces it.
118
119## Shared read position and history queries
120
121The read position is shared, not per principal. `MergeRequestDetail.HeadUnread`
122is a fact: the nonzero head differs from that position. The web presentation
123still decides who sees the mark-read button.
124
125Repository comparisons return at most `ports.MaxCompareCommits` (500) commits.
126Push summaries count at most `ports.MaxPushSummaryCommits` (100) commits and
127report whether more exist; ancestry, rather than the bounded list, detects a
128rewrite. Merge-request details include at most `ports.MaxMergeRequestCommits`
129(100) commits. These history queries remain on the merge-request service
130because it owns the merge-git port.
131
132### Review page panels
133
134The main request card ends with a footer of two tabs, Commits and Checks, both
135collapsed by default. Clicking a tab opens its panel, clicking the open tab
136folds it again, clicking the other tab switches. Arrow keys (and Home / End)
137move between the tabs. Without scripts the tabs are anchor links and the URL
138fragment (`#mr-commits`, `#mr-checks`) shows the panel. The checks summary above
139the diff opens the Checks panel and continues to update live. Commit totals use
140`N+` when the branch list is capped: the reader's existing count operation counts all reachable
141ancestors, not the source-minus-target range.
142
143The rail keeps Files (including its `g f` shortcut) and Verdicts. Merge settings
144are read-only information in the More (⋯) menu, available to every viewer.
145Signing-key information is also there when a merge box offers signed modes;
146merge actions remain restricted to their existing permissions.
147
148## Live source-branch updates
149
150A push to the source branch refreshes the web review in place: the diff, files
151rail, commits/checks footer, diff range and merge controls follow the new head.
152The review keeps its visible file/line, folded files and open footer panel.
153The page request still reads only one 25-file window of hunks; the visible
154anchor's window is fetched too if needed, and other windows remain lazy.
155
156While a comment is focused or has unsent edits, the refresh waits. A small
157“branch updated — refreshing after your comment” status explains the delay.
158Sending, cancelling, or reverting the draft and leaving its form lets the
159pending refresh proceed. Refresh never preserves or discards an unsent draft.