1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
//! What:
//! Merges:
//! the word-level second pass,
//! isolated merges and pull handling.
//! Why:
//! Merge code shares fixtures and a journal,
//! so it is kept together.
//!
//! In TS you'd write (pseudocode):
//! ```ts
//! // merge/index.ts: one `export * from './file'` per module below.
//! ```
/// The three-way merge by line and by word that resolves a conflict Git's line merge reports.
/// The conflicted files a merge left, which of them the word pass may re-merge, and the lines that list each merged part.
/// The conflicted files of a merge tree and the reading of `git merge-tree` output into conflicts.
/// How the word-level second pass starts Git.
/// The word-level second pass for merges computed from objects, and the attribute tree those merges read.
/// The word-level second pass after a forwarded merge, rebase, cherry-pick or revert that Git stopped with a conflict.
/// The finish of a stopped operation, like a clean run, after the second pass resolved every conflicted file.
/// Which options make the finish of a stopped operation stop where Git would stop.
/// The `git merge` command lines the wrapper completes in isolation, and those it leaves to native Git.
/// The settling of an isolated merge whose branch moved while it was prepared or applied.
/// The durable intent record of an isolated merge.
/// The raw differences of an isolated merge and the worktree state of each changed path.
/// Recovery of an isolated merge whose process died.
/// The steps shared by the recovery of an interrupted merge and the settling of a moved branch.
/// The commit message of an isolated merge.
/// A pull that merges, read as its fetch and its merge of `FETCH_HEAD`.
/// The refusal findings of an isolated merge.
/// A true merge completed in isolation while the index holds staged changes.
/// The writing half of an isolated merge: the merge tree, the commit and the two-way update.
/// The questions an isolated merge asks Git and the terminal.
/// The values an isolated merge passes between its steps.