gbp-config(1)

💖 gbp-config(1) — or, "how do I ask gbp what it's thinking" 💖

okay bestie, so this is a page from the git-buildpackage Manual (yeah, the whole git-buildpackage fam, they're all here), and it's about the little command that tells you what config values gbp is actually gonna use. it's giving "let me just check the vibes before I commit" energy and honestly? iconic. 🎀

---

✨ NAME ✨

gbp-config — query configuration values 🦋

like, you ask it stuff, it tells you stuff. that's the whole thing.

---

🌸 SYNOPSIS 🌸

gbp config [--version] [--help] [--verbose] [--color=[auto|on|off]]
           [--color-scheme= COLOR_SCHEME] {command.option | command}

---

💅 DESCRIPTION 💅

so gbp config prints values from the configuration files. it interpolates the value for option of command — which is a fancy way of saying it goes and figures out what the value would actually be, and then shows you. no cap. 🔥

---

👑 OPTIONS 👑

• --version — prints the version of the program, i.e. the version of the git-buildpackage suite. you know, for when you're like "wait which one am I even running"
• -v, --verbose — verbose execution. more words, more detail, more for you to read. main character energy for your terminal output 💖
• -h, --help — print help and exit. the classic "help me pls" button 🫶
• --color=[auto|on|off] — whether to use colored output. auto does its own vibe check, on and off are pretty self-explanatory ngl 🌈
• --color-scheme=COLOR_SCHEME — the colors to use in output (only when color is enabled, obviously). the format for COLOR_SCHEME is '<debug>:<info>:<warning>:<error>'. numerical values and color names are accepted, and empty fields imply the default color. for example, --git-color-scheme='cyan:34::' would show debug messages in cyan, info messages in blue and other messages in default (i.e. warning and error messages in red). so basically you're picking each little slot's outfit 💅

---

⭐ EXIT CODES ⭐

when gbp config finishes, it indicates success or failure with its exit code. here's the breakdown, no ambiguity bestie:

• 0 — Success. 🎉 slay, it worked.
• 1 — Failed to parse command line. 💀 you typed something it couldn't make sense of.
• 2 — The value did not exist. 😭 it looked. it was not there.

---

🦋 EXAMPLES 🦋

print the value upstream-branch that gbp buildpackage would use:

$ gbp config buildpackage.upstream-branch
buildpackage.upstream-branch=upstream

print the values of all of the gbp buildpackage options:

$ gbp config buildpackage
buildpackage.upstream-branch=upstream
buildpackage.debian-branch=master
...

see? the "..." is doing so much heavy lifting there. it's giving teaser trailer. 🙈

---

🎀 CONFIGURATION FILES 🎀

several gbp.conf files are parsed to set defaults for the above command-line arguments. head over to the gbp.conf(5) manpage for the details — that's where the lore lives, iykyk.

---

💜 SEE ALSO 💜

• gbp.conf(5) — go read it, bestie, it's literally right there

---

👸 AUTHOR 👸

Guido Günther <agx@sigxcpu.org> — thank you for your service, king 🫡

---

and that's the whole page!! go forth and query your config values, you absolute legend 💖✨

okay so this was gbp-config(1) from the git-buildpackage suite, and the version on the tin is dated 26 May 2026 — mwah, mwah, xoxo, go config your heart out 💅🎀🦋