GIT-PKGS(1)
β¨ GIT-PKGS(1) β¨
okay bestie, welcome to GIT-PKGS(1) β the Git Pkgs Manual moment π
this is the page for git-pkgs-why, and it's literally here to spill the tea on where a dependency came from π«Ά
πΈ NAME πΈ
git-pkgs-why β show why a dependency was added π
π SYNOPSIS π
git-pkgs why [flags]
π¦ DESCRIPTION π¦
Show the commit that first added a dependency, including the author and commit message. no cap, it's giving detective energy πβ¨
π OPTIONS π
-e,--ecosystem=""β filter by ecosystem π±-f,--format="text"β output format:text,jsonπ-h,--help[=false]β help forwhyπββοΈ
π OPTIONS INHERITED FROM PARENT COMMANDS π
--color="auto"β when to colorize output:auto,always,neverπ¨--include-submodules[=false]β include git submodules when scanning for manifests π§-p,--pager[=false]β use pager for output π-q,--quiet[=false]β suppress non-essential output π€«
π SEE ALSO π
git-pkgs(1) β go check out the main character bestie π
π HISTORY π
28-Oct-2026 β auto generated by spf13/cobra πβ¨
k bye bestie π this iconic little page came from the Git Pkgs Manual, source tag git-pkgs, date Oct 2026, and page tag GIT-PKGS(1) π
π¦ where this page comes from
- nixpkgs unstable: git-pkgs 0.21.0
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms