HG(PATHS)

✨ NAME ✨

hg paths β€” show aliases for remote repositories πŸ¦‹


🌸 SYNOPSIS 🌸

hg paths [NAME]

πŸ’– DESCRIPTION πŸ’–

okay so bestie, this command shows you the definition of the symbolic path name NAME. No name? No problem β€” it shows you the definition of all the available names. all of them. the whole roster. πŸ‘‘

The option -q / --quiet is the introvert of the group: when you're searching for NAME, it suppresses all output, and when you're listing every definition, it shows you only the path names. just the names. nothing else. lowkey iconic.

So where do these path names even live? They're defined in the [paths] section of your configuration file, and also in /etc/mercurial/hgrc. And if you run this inside a repository, .hg/hgrc gets used too. ✨

Now, the path names default and default-push? They have special meaning, bestie. When you're doing a push or pull operation, they act as the fallbacks if you didn't specify a location on the command-line. When default-push is set, it gets used for push and default gets used for pull; otherwise default is the fallback for both. And when you clone a repository, the clone source gets written as default in .hg/hgrc. no cap. πŸŽ€

⚠️ heads up: default and default-push apply to all inbound (e.g. hg incoming) and outbound (e.g. hg outgoing, hg email and hg bundle) operations. every single one.

See hg help urls for more info. 🫢

πŸŽ€ Template

The following keywords are supported. See also hg help templates.

  • name β€” String. Symbolic name of the path alias.
  • pushurl β€” String. URL for push operations.
  • url β€” String. URL or directory path for the other operations.

Returns 0 on success. πŸ’…


⭐ OPTIONS ⭐

  • -T, --template <TEMPLATE> β€” display with template

and that's the whole vibe, bestie πŸ’œ this page signs off as HG(PATHS) β€” that's the source/version and date right there, literally just the name in the footer, and honestly? it ate. go forth and slay your remote paths πŸŒˆπŸ‘‘