GIT-PKGS(1)
π¦ GIT-PKGS(1) β the Git Pkgs Manual, bestie edition π¦
okay so you're looking at git-pkgs, and this specific page is all about git-pkgs-update, the glow-up-your-dependencies command. no cap, it's lowkey the most useful one. let's get into it π
β¨ NAME β¨
git-pkgs-update β update dependencies. that's it, that's the vibe. π
β¨ SYNOPSIS β¨
git-pkgs update [package] [flags]
π DESCRIPTION π
So here's the tea: git-pkgs update updates your dependencies using the detected package manager (it sniffs out which one you're using, main character energy fr fr).
- If you hand it a package name? Only that one package gets updated. Just the one. VIP treatment. π
- If you don't? Every single dependency gets updated. the whole squad. π₯
Here are the examples, exactly as they live in the wild:
git-pkgs update # update all dependencies
git-pkgs update lodash # update specific package
git-pkgs update -e npm # only update npm ecosystem
git-pkgs update --all # update all (for managers that need explicit flag)
Periodt. π«Ά
πΈ OPTIONS πΈ
okay bestie, here's the full menu, nothing skipped, every single flag:
--all[=false]β Update all dependencies. this one's for the managers likemixthat need you to explicitly say--allbefore they'll do anything. they're dramatic like that. π--dry-run[=false]β Show what would be run without actually executing it. a little peek, no commitment. π-e,--ecosystem=""β Filter to a specific ecosystem. narrow the vibe check down to one ecosystem only.-x,--extra=[]β Extra arguments to pass to the package manager. slip your fave flags through the side door. β¨-h,--help[=false]β help for update. the classic "what does this even do" button.-m,--manager=""β Override the detected package manager. and yes, it takes precedence over-eβ so if you set both,-mwins. no tie-breakers, no drama,-mis just that girl. π-t,--timeout=10m0sβ Timeout for the update operation. default is10m0s. if it's taking forever, that's on the clock, not on you. β
π¦ OPTIONS INHERITED FROM PARENT COMMANDS π¦
these ones come from the parent command β still yours to use, they're just visiting:
--color="auto"β When to colorize output. your options areauto,always,never. pick your aesthetic. π--include-submodules[=false]β Include git submodules when scanning for manifests. don't forget the little nested babies. π-p,--pager[=false]β Use pager for output. for when the output is giving "I need to scroll". π-q,--quiet[=false]β Suppress non-essential output. sometimes you just want silence, and that's valid. π€«
π SEE ALSO π
git-pkgs(1)β go say hi to the parent, iykyk π
π HISTORY π
28-Oct-2026 β Auto generated by spf13/cobra. not me being literally auto-generated, it's giving β¨machine-madeβ¨ and honestly? iconic.
so yeah, that's the whole page. this git-pkgs manual page is dated Oct 2026, and it was brought to you by the fine folks behind the Git Pkgs Manual β mwah, thank you for coming to my ted talk, go update those dependencies bestie π
π¦π
π¦ 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