HG(BUNDLE)

💖 hg bundle — the manual, but make it cute 💖

okay bestie, welcome to the HG(BUNDLE) page, aka the part of the hg manual that teaches you how to create a bundle file. it's giving "pack your bags, we're moving repos" energy and honestly? iconic. let's get into it 🎀

✨ NAME ✨

hg bundle — create a bundle file 🦋

✨ SYNOPSIS ✨

hg bundle [-f] [-t BUNDLESPEC] [-a] [-r REV]... [--base REV]... FILE [DEST]...

✨ DESCRIPTION ✨

so basically: you're generating a bundle file that's full of data meant to be transferred over to another repository. it's a little care package of commits, fr fr 💌

if you want a bundle with literally every changeset in it, use -a/--all (or, same vibe, --base null). but if you don't do that, hg assumes your destination already has all the nodes you named with the --base parameters. and if you don't do that either? hg assumes the repo already has all the nodes in destination — or default-push/default if you didn't name a destination at all — where destination means the repositories you hand over through the DEST option. it's a whole chain of assumptions and hg is just out here trusting you 🫶

you can change the bundle format with the -t/--type option. the full lore on that format lives in hg help bundlespec. and by default? the most appropriate format gets used and compression defaults to bzip2. slay.

once your bundle file exists, you can move it around however you want (conventional means, nothing fancy ✨) and then apply it to another repository with the unbundle or pull command. this is the move when direct push and pull aren't available, or when exporting an entire repository is just... not the vibe you're going for.

and here's the part that matters: applying bundles preserves all changeset contents, including:

• permissions
• copy/rename information
• revision history

she keeps receipts. no cap. 👑

Returns 0 on success, 1 if no changes found.

✨ OPTIONS ✨

• --exact — compute the base from the revision you specified. precise queen behavior 💅
• -f, --force — run it even when the destination is unrelated. chaotic but sometimes necessary 🙈
• -r,--rev <REV[+]> — a changeset intended to be added to the destination
• -b,--branch <BRANCH[+]> — a specific branch you would like to bundle 🌸
• --base <REV[+]> — a base changeset assumed to be available at the destination
• -a, --all — bundle all changesets in the repository. the whole entire thing, bestie 💖
• -t,--type <TYPE> — bundle compression type to use (default: bzip2)
• -e,--ssh <CMD> — specify ssh command to use
• --remotecmd <CMD> — specify hg command to run on the remote side
• --insecure — do not verify server certificate (ignoring web.cacerts config)

🚨 psst — any option marked with [+] can be specified multiple times. stack 'em up, it's fine 🧚

okay that's the whole page, you ate it up, go forth and bundle responsibly ✨💜

later bestie — this was the HG(BUNDLE) page, and that's a wrap on the manual 🌈🎀👑