GIT-PKGS(1)
π GIT-PKGS(1) π
okay so welcome to the Git Pkgs Manual bestie, specifically the page for git-pkgs-bisect-good β yes that name is a mouthful, we love her anyway π
β¨ NAME β¨
git-pkgs-bisect-good β mark commits as good π
β¨ SYNOPSIS β¨
git-pkgs bisect good [...] [flags]
β¨ DESCRIPTION β¨
okay so here's the vibe: you're bisecting, right? and you gotta tell git which commits are good β meaning they came before the problem showed up. this command marks one or more commits as good. simple as that, no cap π¦
β¨ OPTIONS β¨
-h,--help[=false]β shows the help forgood. iconic, honestly π«Ά
β¨ OPTIONS INHERITED FROM PARENT COMMANDS β¨
these bad girls come from the parent command, so you get 'em for free:
--color="auto"β decides when to colorize the output. your choices areauto,always,neverπ--include-submodules[=false]β pulls git submodules into the mix when it's scanning for manifests π-p,--pager[=false]β uses the pager for output, if that's your thing β¨-q,--quiet[=false]β suppresses all the non-essential output so it's nice and chill π€«
β¨ SEE ALSO β¨
git-pkgs-bisect(1)β the parent, the main character, go say hi π
β¨ HISTORY β¨
28-Oct-2026 β auto generated by spf13/cobra π€ (not me, I would never, but slay)
and that's the whole page bestie, you ate that π β¨
signing off from the git-pkgs manual, Oct 2026 edition ππ¦ see u in the next one!! π
π¦ 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