@@ -101,7 +101,7 @@ merge::
101101 any) into the current notes ref (called "local").
102102+
103103If conflicts arise and a strategy for automatically resolving
104- conflicting notes (see the -s/--strategy option ) is not given,
104+ conflicting notes (see the "NOTES MERGE STRATEGIES" section ) is not given,
105105the "manual" resolver is used. This resolver checks out the
106106conflicting notes in a special worktree (`.git/NOTES_MERGE_WORKTREE`),
107107and instructs the user to manually resolve the conflicts there.
@@ -183,6 +183,7 @@ OPTIONS
183183 When merging notes, resolve notes conflicts using the given
184184 strategy. The following strategies are recognized: "manual"
185185 (default), "ours", "theirs", "union" and "cat_sort_uniq".
186+ This option overrides the "notes.mergeStrategy" configuration setting.
186187 See the "NOTES MERGE STRATEGIES" section below for more
187188 information on each notes merge strategy.
188189
@@ -247,6 +248,9 @@ When done, the user can either finalize the merge with
247248'git notes merge --commit', or abort the merge with
248249'git notes merge --abort'.
249250
251+ Users may select an automated merge strategy from among the following using
252+ either -s/--strategy option or configuring notes.mergeStrategy accordingly:
253+
250254"ours" automatically resolves conflicting notes in favor of the local
251255version (i.e. the current notes ref).
252256
@@ -310,6 +314,20 @@ core.notesRef::
310314 This setting can be overridden through the environment and
311315 command line.
312316
317+ notes.mergeStrategy::
318+ Which merge strategy to choose by default when resolving notes
319+ conflicts. Must be one of `manual`, `ours`, `theirs`, `union`, or
320+ `cat_sort_uniq`. Defaults to `manual`. See "NOTES MERGE STRATEGIES"
321+ section above for more information on each strategy.
322+ +
323+ This setting can be overridden by passing the `--strategy` option.
324+
325+ notes.<name>.mergeStrategy::
326+ Which merge strategy to choose when doing a notes merge into
327+ refs/notes/<name>. This overrides the more general
328+ "notes.mergeStrategy". See the "NOTES MERGE STRATEGIES" section above
329+ for more information on each available strategy.
330+
313331notes.displayRef::
314332 Which ref (or refs, if a glob or specified more than once), in
315333 addition to the default set by `core.notesRef` or
@@ -331,7 +349,8 @@ environment variable.
331349notes.rewriteMode::
332350 When copying notes during a rewrite, what to do if the target
333351 commit already has a note. Must be one of `overwrite`,
334- `concatenate`, and `ignore`. Defaults to `concatenate`.
352+ `concatenate`, `cat_sort_uniq`, or `ignore`. Defaults to
353+ `concatenate`.
335354+
336355This setting can be overridden with the `GIT_NOTES_REWRITE_MODE`
337356environment variable.
@@ -368,7 +387,7 @@ does not match any refs is silently ignored.
368387'GIT_NOTES_REWRITE_MODE'::
369388 When copying notes during a rewrite, what to do if the target
370389 commit already has a note.
371- Must be one of `overwrite`, `concatenate`, and `ignore`.
390+ Must be one of `overwrite`, `concatenate`, `cat_sort_uniq`, or `ignore`.
372391 This overrides the `core.rewriteMode` setting.
373392
374393'GIT_NOTES_REWRITE_REF'::
0 commit comments