GIT-BUG(1)

📦
version 0.11.0 · 2 versions
, in arch rolling, nixpkgs unstable

💅 GIT-BUG(1) — the git-bug version page, bestie edition 🎀

okay so real quick — this whole page is a slice of the git-bug(1) manual, specifically the git-bug-version subcommand. It's short, it's sweet, it's giving "one job and it does it." Let's go. ✨

🌸 NAME 🌸

git-bug-version — print version information. That's it. That's the whole assignment. 💖

🦋 SYNOPSIS 🦋

git-bug version [flags]

literally just type that and it tells you about itself. iconic.

✨ DESCRIPTION ✨

Print version information. no cap, that's the description.

The format it spits out is:

git-bug  [commit[/dirty]]

Format description — let's break down what those bits mean, bestie:

  • The version part ` may be one of:
    • a semantic version string, prefixed with a v, e.g. v1.2.3 👑
    • "undefined" (if it wasn't provided, or it was built with an invalid version string) 💀
  • [commit], if present, is the commit hash that was checked out during the build. It may be suffixed with '/dirty' if there were local file modifications. That suffix lowkey means your build has been patched, or modified in some way from the commit. 🙈
  • is the version of the go compiler used for the build.
  • is the target platform (GOOS).
  • is the target architecture (GOARCH).
🫶 heads up: in the source page those last three bits are blank — the placeholder names just aren't there. So yeah, that's a formatting thing in the original, not me being lazy. Not me forgetting, I promise. 😭

🎀 OPTIONS 🎀

  • -h, --help[=false] — help for version. your little "what does this even do" button. main character energy for beginners. 💜

🌈 EXAMPLE 🌈

git bug version

see? told you. one line. slay. 🔥

👑 SEE ALSO 👑

git-bug(1) — the big one, the parent, the whole vibe. go read it. iykyk.

that's the whole page, bestie — generated from git-bug's source 💫 (it's the ... bit in the original, bless) and dated Apr 2019, footer and all. go run git bug version and feel something. 💅✨

📦 where this page comes from