NBMERGE(1)

NBMERGE(1) 💖

okay bestie, welcome to User Commands — this is the manual for nbmerge, and yes she's giving main character energy, come sit with me 🫶

---

✨ NAME ✨

nbmerge — merge two Jupyter notebooks 💅

---

🌸 DESCRIPTION 🌸

okay so here's the whole vibe, literally the entire usage line, no cap:

usage: nbmerge [-h] [--version] [--config]
              [--log-level {DEBUG,INFO,WARN,ERROR,CRITICAL}] [-s] [-o] [-a]
              [-m] [-i] [-d] [--merge-strategy
              {inline,use-base,use-local,use-remote}] [--input-strategy
              {inline,use-base,use-local,use-remote}] [--output-strategy
              {inline,use-base,use-local,use-remote,remove,clear-all}]
              [--no-ignore-transients] [--no-color] [--no-git] [--no-use-diff]
              [--out OUT] [--decisions] [base] local remote

So what she actually does: she merges two Jupyter notebooks, local and remote, that share a common ancestor called base. And if you just... don't pass a base? 🦋 She uses an empty notebook as the base instead. Iconic of her honestly.

---

🎀 positional arguments 🎀

• base — the base notebook filename, the ancestor, the origin story fr.
• local — the local modified notebook filename.
• remote — the remote modified notebook filename.

---

💅 options 💅

• -h, --help — show this help message and exit. the classic.
• --version — show program's version number and exit.
• --config — list the valid config keys and their current effective values. it's giving receipts ✨
• --log-level {DEBUG,INFO,WARN,ERROR,CRITICAL} — set the log level by name.
• --merge-strategy {inline,use-base,use-local,use-remote} — the merge strategy to use.
• --input-strategy {inline,use-base,use-local,use-remote} — the merge strategy to use for inputs. heads up: this overrides merge-strategy for inputs 👑
• --output-strategy {inline,use-base,use-local,use-remote,remove,clear-all} — the merge strategy to use for outputs. and yeah, it overrides merge-strategy for outputs too.
• --no-ignore-transients — disallow deletion of transient data such as outputs and execution counts in order to resolve conflicts. like, no deleting the little extras to make peace 😤
• --no-color — prevent use of ANSI color code escapes for text output.
• --no-git — prevent use of git for formatting diff/merge text output.
• --no-use-diff — prevent use of diff/diff3 for formatting diff/merge text output.
• --out OUT — if supplied, the merged output is written to this file. otherwise it is printed to the terminal. so OUT is the file, mmkay? 🍓
• --decisions — print a human-readable summary of conflicted merge decisions instead of merging the notebook. she spills the tea instead of doing the merge, obsessed.

---

🧚 ignorables 🧚

Set which parts of the notebook (not) to process. like a vibe check but for notebook sections ✨

• -s, --sources, -S, --ignore-sources — process/ignore sources.
• -o, --outputs, -O, --ignore-outputs — process/ignore outputs.
• -a, --attachments, -A, --ignore-attachments — process/ignore attachments.
• -m, --metadata, -M, --ignore-metadata — process/ignore metadata.
• -i, --id, -I, --ignore-id — process/ignore identifiers.
• -d, --details, -D, --ignore-details — process/ignore details not covered by other options.

ngl, the lowercase flag means process and the uppercase one means ignore. she said twin sisters, opposite attitudes 💀

---

and that's the whole page, bestie!! 🎀 this was nbmerge 4.0.4, dated February 2026 — mwah, love her, go merge some notebooks fr fr 💖✨🦋