HG(ANNOTATE)

💖 hg annotate 💖

okay bestie, welcome to the hg annotate page — yes it's from the HG(ANNOTATE) manual, and yes it's about to become your new obsession. it's literally the "who wrote this line and when" command. no cap. 🦋

---

✨ NAME ✨

hg annotate — show changeset information by line for each file 👑

---

✨ SYNOPSIS ✨

hg annotate [-r REV] [-f] [-a] [-u] [-d] [-n] [-c] [-l] FILE...

---

✨ DESCRIPTION ✨

okay so here's the vibe: this command lists the changes in files, and it shows you the revision id responsible for each line. every single line gets a lil receipt of who's accountable for it. 💅

it's useful for discovering when a change was made and by whom. detective mode: activated. 🔍

if you include --file, --user, or --date, the revision number is suppressed unless you also include --number. so like, don't be shocked when the rev number ghosts you — you did that. 😭

without the -a/--text option, annotate will avoid processing files it detects as binary. with -a, annotate will annotate the file anyway — although the results will probably be neither useful nor desirable. so like... you can, but should you? 🫣

use -L/--line-range FILE,M:N options to filter the output to the lines from M to N in FILE. this option is incompatible with --no-follow and cannot be combined with file pattern arguments. when combined with --rev, the line ranges refer to the state of the file at the requested revision. noted, bestie. 📝

🌸 Template 🌸

the following keywords are supported in addition to the common template keywords and functions. see also hg help templates.

• lines — list of lines with annotation data. 📋
• path — String. Repository-absolute path of the specified file.

and each entry of {lines} provides the following sub-keywords in addition to {date}, {node}, {rev}, {user}, etc.

• line — String. Line content.
• lineno — Integer. Line number at that revision.
• path — String. Repository-absolute path of the file at that revision.

see hg help templates.operators for the list expansion syntax. 🧚

returns 0 on success. slay. ✨

---

✨ OPTIONS ✨

• -r, --rev <REV> — annotate the specified revision 🎯
• --follow — follow copies/renames and list the filename (DEPRECATED) 💀
• --no-follow — don't follow copies and renames 🙅
• -a, --text — treat all files as text 📄
• -u, --user — list the author (long with -v) 🧑
• -f, --file — list the filename 📁
• -d, --date — list the date (short with -q) 📅
• -n, --number — list the revision number (default) 🔢
• -c, --changeset — list the changeset 📦
• -l, --line-number — show line number at the first appearance 🔎
• --skip <REV[+]> — revset to not display (EXPERIMENTAL) 🧪
• -L, --line-range <FILE,RANGE[+]> — follow line range of specified file (EXPERIMENTAL) 🧪
• -w, --ignore-all-space — ignore white space when comparing lines 🫥
• -b, --ignore-space-change — ignore changes in the amount of white space 🫥
• -B, --ignore-blank-lines — ignore changes whose lines are all blank 🫥
• -Z, --ignore-space-at-eol — ignore changes in whitespace at EOL 🫥
• -I, --include <PATTERN[+]> — include names matching the given patterns ✅
• -X, --exclude <PATTERN[+]> — exclude names matching the given patterns ❌
• -T, --template <TEMPLATE> — display with template 🎨

[+] marked option can be specified multiple times. yes queen, stack 'em. 🌈

---

✨ ALIASES ✨

blame — because sometimes you just gotta point fingers, and this command lets you do it with data. 😌💅

---

and that's the whole page, bestie!! 💖 thanks for reading the HG(ANNOTATE) manual with me — this was the hg annotate page, sourced from the HG(ANNOTATE) manual. go forth and annotate responsibly. mwah. 🎀🦋✨