GIT-PKGS(1)

πŸ“¦
version 0.21.0 Β· 2 versions
, in nixpkgs unstable

πŸ’… GIT-PKGS-DIFF πŸ¦‹

okay so bestie, listen β€” this is the git-pkgs manual page, and today's main character is git-pkgs-diff. like, yes, the whole Git Pkgs Manual vibe is a thing, but this page is specifically about the diff subcommand, and it's giving dependency-comparison excellence. no cap.


✨ NAME ✨

git-pkgs-diff β€” the icon that compares dependencies between commits or your working tree 🫢


🌸 SYNOPSIS 🌸

git-pkgs diff [from..to] [flags]

πŸ’– DESCRIPTION πŸ’–

so what does it do? it compares dependencies between two commits, refs, or the working tree. that's it, that's the whole slay.

run it with no arguments and it compares HEAD against the working tree β€” literally the same energy as git diff, but for your deps. iykyk πŸ’…

it also speaks range syntax (main..feature), or if ranges aren't your vibe, you can be explicit with the --from/--to flags. both paths are valid, pick your fighter ✨


πŸŽ€ OPTIONS πŸŽ€

  • --by="manifest" β€” how should we match up your dependencies? options are manifest or ecosystem. this is the default, bestie.
  • -e, --ecosystem="" β€” filter by ecosystem. empty by default, so you're seeing everything until you say otherwise 🌈
  • -f, --format="text" β€” the output format, queen. text (the default) or json for when you're feeling ✨machine-readable✨
  • --from="" β€” the starting commit. defaults to HEAD, obviously πŸ’β€β™€οΈ
  • -h, --help[=false] β€” help for diff. it's giving "i just need to know what's happening" 🫢
  • --kind="" β€” filter by manifest kind: manifest or lockfile. ngl this one's lowkey underrated
  • --stat[=false] β€” show aggregate dependency change counts. the receipts, basically 🧾
  • --summary[=false] β€” also shows aggregate dependency change counts. yeah, same description as --stat β€” that's what the page says, so that's what you get, no notes 😭
  • --to="" β€” the ending commit. defaults to the working tree πŸ’–
  • -t, --type="" β€” filter by dependency type (runtime, development, etc.). the "etc." is doing a lot of heavy lifting here but we respect it πŸ‘‘

πŸ‘‘ OPTIONS INHERITED FROM PARENT COMMANDS πŸ‘‘

these come from the parent, so they're not technically diff's, but they're absolutely invited to the party:

  • --color="auto" β€” when to colorize output: auto, always, never. default is auto πŸ’…
  • --include-submodules[=false] β€” include git submodules when scanning for manifests. the submodules get to come too πŸ¦‹
  • -p, --pager[=false] β€” use pager for output. for when the output is a whole novel πŸ“–
  • -q, --quiet[=false] β€” suppress non-essential output. shhh 🀫

🌟 SEE ALSO 🌟

  • git-pkgs(1) β€” the parent, the origin story, the icon herself πŸŽ€

⭐ HISTORY ⭐

28-Oct-2026 β€” Auto generated by spf13/cobra. not me being a whole cobra-generated page, it's fine, it's iconic πŸ”₯


heads up bestie: this page was auto generated by spf13/cobra on 28-Oct-2026, so if something looks a little machine-made, that's why πŸ’€

and that's the page!! tysm for reading, you're gonna do great with git-pkgs diff, fr fr 🫢✨ this was git-pkgs, from Oct 2026, signing off β€” mwah πŸ’–

πŸ“¦ where this page comes from