GHI(1)
π GHI(1) β the GHI manual, bestie edition π
okay so you're looking at the GHI(1) page from the GHI Manual and honestly? you're about to have a great time. sit down, grab a boba, let's go π§
β¨ NAME β¨
ghi β the stupid issue tracker
like yes it's called "stupid" and yes it's iconic for that. moving on π
πΈ SYNOPSIS πΈ
ghi [--version] [-p|--paginate|--no-pager] [--help] command [args]
[ -- [user/]repo]]
that's the whole shape of it. command first, arguments after, and if you wanna point at a specific repo you tack it on at the end after the --. slay. β
π¦ DESCRIPTION π¦
GHI is the alphabetical acronym for GitHub Issues, and no I will not be explaining why the acronym is alphabetical, that's just the lore. what it actually does is give you an easy way to manage your issues from the comfort of the command line and your editor of choice β which is the correct balance of cool and cozy, fr fr. π
GHI should look familiar if you're familiar with Git. that's the whole design language, it's giving "you already know this, bestie."
here's the vibe check on how it picks a repo:
- when you invoke it from a repository directory that has a GitHub remote, GHI will work with that repository's issues by default β no extra typing, we love an effortless queen π
- otherwise, GHI will work with your global issues, or with a repository you specify in its terminating arguments. so you're never stuck, there's always a fallback π«Ά
and the command? it's either the name of a GHI command (scroll down, they're all listed) or an alias. that's it, that's the rule. β¨
π₯ OPTIONS π₯
--versionβ prints the GHI version number. short, sweet, does exactly what it says π--helpβ prints the synopsis and a list of commonly-used commands. and if you name a GHI command with it, this option will bring up the manual page for that command. so--helpis basically the "help me help you" flag. seeghi-help(1)for more information π-p,--paginateβ pipes all output intolessif standard output is a terminal. long output? contained. periodt.--no-pagerβ do not pipe output into a pager. for the girlies who want it all dumped straight to the terminal, respect π«‘--[no-]colorβ toggles colorized output. yes color, no color, you decide, main character energy π
π GHI COMMANDS π
here's the roster, alphabetically iconic, every single one:
ghi-assign(1)β assign an issue to yourself (or someone else). delegation is self-care πghi-close(1)β close an issue. bye bestie, resolved. πghi-lock(1)β lock an issue's conversation, limiting it to collaborators. respectfully, this conversation is now invite-only πghi-unlock(1)β unlock an issue's conversation, opening it to all viewers. doors open, come on in πghi-comment(1)β leave a comment on an issue. say your piece, queen π£οΈghi-config(1)β configure GHI. the setup era βοΈghi-edit(1)β modify an existing issue. glow-up time β¨ghi-label(1)β create, list, modify, or delete labels. organization is a love language π·οΈghi-list(1)β list your issues (or a repository's). the scroll πghi-milestone(1)β manage project milestones. goals, literally π―ghi-open(1)β open (or reopen) an issue. we're so back π₯ghi-show(1)β show an issue's details. the receipts π
π ENVIRONMENT VARIABLES π
various GHI commands use these env vars, so pay attention bestie, they're doing a lot of the work behind the scenes:
GHI_REPOβ the GitHub repository to be used by the issued GHI command.GHI_TOKENβ the OAuth access token used to authenticate you. your little key to the kingdom πGHI_PAGERβ this one overrides$GIT_PAGERand$PAGER. ngl, this next bit is important: if it is set to an empty string or to the value"cat", git will not launch a pager. no pager, no problem πGHI_EDITORβ overrides$GIT_EDITOR,$VISUAL, and$EDITOR. your editor, your rules βοΈGITHUB_USERβ your GitHub username: used to authenticate and identify you. it's giving β¨identityβ¨GITHUB_PASSWORDβ if you store your GitHub password in an environment variable, GHI will automatically attempt to fetch an access token using it. convenient! (be normal about where you put your password though π)
and here's the cute little plot twist: all environment variables may also be stored in Git configuration files, where the variable is in lowercase form and the underscore becomes a period. so$GHI_REPOwould become theghi.repooption. same energy, different outfit π
π AUTHORS π
GHI is maintained by Stephen Celis. a full list of contributors can be found at https://github.com/stephencelis/ghi/contributors β go say hi to the whole crew π«Ά
π§ REPORTING BUGS π§
found something cursed? drop it here:
ghi open -- stephencelis/ghi
or visit https://github.com/stephencelis/ghi/issues. either way, tell them everything, they wanna know π
β and that's the page!! written by Stephen Celis, dated June 2016, living at the bottom of GHI(1) forever. go forth and manage your issues, bestie β no cap, you're gonna slay π
π
π¦ where this page comes from
- alpine 3.24: ghi-doc 1.2.1-r2 Β· MIT
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms