HG(OUTGOING)
πΈ NAME πΈ
hg outgoing β the little command that shows you the changesets that are not in the destination. iykyk, it's literally the "what would I be pushing rn" check. π
β¨ SYNOPSIS β¨
hg outgoing [-M] [-p] [-n] [-f] [-r REV]... [DEST]...
π¦ DESCRIPTION π¦
okay so bestie, here's the vibe: hg outgoing shows you all the changesets that aren't found in the destination repo you pointed at β or, if you didn't point anywhere, in the default push location. These are exactly the changesets that would get pushed if you actually requested a push. It's a sneak peek. A trailer. A "preview the drop before it drops". π
Need the deets on what counts as a valid destination format? Go look at pull. fr fr, that's where the lore lives.
π Bookmark comparison (the fun part) π
With -B / --bookmarks, you get the result of the bookmark comparison between your local repo and the remote one. And if you add -v / --verbose, it also shows you the status for each bookmark, like this:
BM1 01234567890a added
BM2 deleted
BM3 234567890abc advanced
BM4 34567890abcd diverged
BM5 4567890abcde changed
Now, what actually happens when you push depends on the status of each bookmark, so let's break it down one by one:
addedβ push with-Bwill create it. brand new bookmark, main character debut β¨deletedβ push with-Bwill delete it. gone, girl πadvancedβ push will update it. it moved forward, slay.divergedβ push with-Bwill update it.changedβ push with-Bwill update it.
π«Ά From the point of view of pushing behavior, bookmarks that exist only in the remote repository are treated as deleted, even if they were in fact added remotely. that's just how it is, no cap.
And the receipts: returns 0 if there are outgoing changes, 1 otherwise. periodt.
π OPTIONS π
-f,--forceβ run it even when the destination is unrelated. chaotic? maybe. but it works.-r,--rev <REV[+]>β a changeset intended to be included in the destination.-n,--newest-firstβ show newest record first. freshest first, obviously π-B,--bookmarksβ compare bookmarks.-b,--branch <BRANCH[+]>β a specific branch you would like to push.-p,--patchβ show patch.-g,--gitβ use git extended diff format.-l,--limit <NUM>β limit number of changes displayed.-M,--no-mergesβ do not show merges.--statβ output diffstat-style summary of changes.-G,--graphβ show the revision DAG.--style <STYLE>β display using template map file (DEPRECATED). yes it's deprecated, don't come for me π-T,--template <TEMPLATE>β display with template.-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 (ignoringweb.cacertsconfig). β οΈ insecure means insecure, bestie, tread carefully.-S,--subreposβ recurse into subrepositories.
π§ the [+] marked option can be specified multiple times. stack 'em, queen.
π ALIASES π
outβ the short lil nickname. use it, it's cute.
and that's the whole HG(OUTGOING) page, bestie π straight from the Mercurial manual β no version stamp or date on this one, so consider it timeless β¨ go forth and check your outgoing like the icon you are π
π¦ where this page comes from
- arch rolling: mercurial 7.2.4-1 Β· GPL
- fedora 43: mercurial 7.1.1-1.fc43 Β· GPL-2.0-or-later
- fedora 43: mercurial 7.1.1-2.fc43 Β· GPL-2.0-or-later
- fedora 44: mercurial 7.2-1.fc44 Β· GPL-2.0-or-later
- fedora 44: mercurial 7.2.4-1.fc44 Β· GPL-2.0-or-later
- nixos 26.05: mercurial 7.1.2
- nixos 26.05: mercurial-full 7.1.2
- nixpkgs unstable: mercurial 7.2.2
- nixpkgs unstable: mercurial-full 7.2.2
- opensuse-leap 16.0: mercurial 7.0.1-160000.2.2 Β· GPL-2.0-or-later
- opensuse-leap 16.0: mercurial 7.0.1-160000.2.2 Β· GPL-2.0-or-later
- opensuse-leap 16.0: mercurial 7.0.1-160000.2.2 Β· GPL-2.0-or-later
- opensuse-leap 16.0: mercurial 7.0.1-160000.2.2 Β· GPL-2.0-or-later
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms