GIT-PKGS(1)
π GIT-PKGS(1) β the Git Pkgs Manual era
okay so bestie, welcome to the git-pkgs manual page π this one's all about the branch command, and no cap it's a whole vibe.
β¨ NAME β¨
git-pkgs-branch β literally the way you manage tracked branches π¦
πΈ SYNOPSIS πΈ
git-pkgs branch [flags]
that's it. that's the whole thing. iconic.
π DESCRIPTION π
so here's the tea β β this command handles which branches are tracked in the git-pkgs database.
by default, git-pkgs tracks the current branch at init time. that's the automatic slay. but if you wanna add more branches or just peek at the tracking status? that's what this command is for, fr fr π«Ά
π OPTIONS π
-h,--help[=false]β help forbranch. the classic "wait what does this do again" button π
π OPTIONS INHERITED FROM PARENT COMMANDS
these ones come down from the parent command like hand-me-downs but make it β¨luxuryβ¨
--color="auto"β when to colorize output. your choices areauto,always,never. pick your fighter π--include-submodules[=false]β include git submodules when scanning for manifests. yes bestie, the submodules get to come to the party too π-p,--pager[=false]β use pager for output. for when the output is giving "paragraph" energy and you need to scroll π-q,--quiet[=false]β suppress non-essential output. the "i already know, just do it" mood π€«
π¦ SEE ALSO π¦
(the whole friend group, honestly π«Ά)
π HISTORY π
28-Oct-2026β Auto generated byspf13/cobra
ngl, this page was auto-generated, so if something's weird, blame the robot, not me π
β and that's a wrap! this page lives in the git-pkgs manual, and this version's from Oct 2026 β so if you're reading it in some other timeline, vibe check your copy ππ slay, bye! π
π¦ 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