HG(PULL)

📦
version 7.2.4 · 2 versions
, in arch rolling, fedora 44, nixpkgs unstable

💅 HG(PULL) — aka hg pull

okay bestie, gather round, because this one is the move. this is the manual page for hg pull, and yes it's giving "I'm about to change your whole repo" energy. let's go 🫶

✨ NAME ✨

hg pull — pull changes from the specified source

like... it goes and gets the changes. from wherever you told it. that's the whole job. 💖

🌸 SYNOPSIS 🌸

hg pull [-u] [-f] [-r REV]... [-e CMD] [--remotecmd CMD] [SOURCE]...

🦋 DESCRIPTION 🦋

So the vibe is: pull changes from a remote repository into a local one. That's it, that's the plot. 💫

It finds all the changes from the repository at the path or URL you specified, and adds them to a local repository — and that local repo is the current one, unless you specified -R. By default, it does not update the copy of the project in the working directory. So your files? Untouched. Your history? Fed. no cap.

When cloning from servers that support it, Mercurial may fetch pre-generated data. And when that happens, heads up: hooks operating on incoming changesets and changegroups may fire more than once — once for each pre-generated bundle, and also for any additional remaining data. 😭 See hg help -e clonebundles for more.

Wanna peek before you commit to the bit? Use hg incoming if you want to see what would have been added by a pull at the time you issued this command. And if you then decide, okay actually yes, add those changes to the repository, you should use hg pull -r X where X is the last changeset listed by hg incoming. iconic little workflow, tbh.

If SOURCE is omitted, the 'default' path will be used. See hg help urls for more information. 🧚

If multiple sources are specified, they will be pulled sequentially as if the command was run multiple times. And if --update is specified, the command will stop at the first failed --update. so like, one strike and we're out. 💀

Specifying bookmark as . is equivalent to specifying the active bookmark's name. lowkey elegant.

You can use the --remote-hidden flag to pull changesets hidden on the remote. Real talk though: this flag is "best effort", and will only work if the server supports the feature and is configured to allow the user to access hidden changesets. This option is experimental and backwards compatibility is not guaranteed. 🙈 so, y'know, don't build your whole life on it.

Returns 0 on success, 1 if an update had unresolved files.

🌈 the exit codes matter bestie, don't skip them

👑 OPTIONS 👑

  • -u, --update — update to new branch head if new descendants were pulled
  • -f, --force — run even when remote repository is unrelated
  • --confirm — confirm pull before applying changes
  • -r, --rev <REV[+]> — a remote changeset intended to be added
  • -B, --bookmark <BOOKMARK[+]> — bookmark to pull
  • -b, --branch <BRANCH[+]> — a specific branch you would like to pull
  • --remote-hidden — include changesets hidden on the remote (EXPERIMENTAL)
  • -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)
[+] marked option can be specified multiple times

and that's the whole page, bestie. you ate. 🎀

later, legend — this was the hg pull page from the Mercurial manual, footer and all just sitting there saying HG(PULL) with absolutely no version or date attached, which is honestly such a minimalist slay of it. 💜

📦 where this page comes from