GitHub Issues on the command line. Use your
$EDITOR, not your browser.
brew install ghi
curl -sL https://raw.githubusercontent.com/stephencelis/ghi/master/ghi > ghi && \ chmod 755 ghi && \ mv ghi /usr/local/bin
gem install ghi
usage: ghi [--version] [-p|--paginate|--no-pager] [--help] <command> [<args>] [ -- [<user>/]<repo>] The most commonly used ghi commands are: list List your issues (or a repository's) show Show an issue's details open Open (or reopen) an issue close Close an issue edit Modify an existing issue comment Leave a comment on an issue label Create, list, modify, or delete labels assign Assign an issue to yourself (or someone else) milestone Manage project milestones See 'ghi help <command>' for more information on a specific command.
- Where does ghi look for issues?
By default, ghi looks for GitHub issues by resolving the current working
directory's repository: first it looks for an
upstream remote, then it
You can override the repository ghi uses by setting the local
git configuration variable:
$ git config ghi.repo username/reponame $ ghi list # username/reponame open issues ...
- How do I specify a GitHub enterprise host?
Just run the following inside your terminal and you'll be good to go:
git config github.host address_of_your_enterprise_host
- How do I enable the pretty colored output?
Make sure your terminal is configured to display 256 colors. You can
check this by running
tput colors, which should return
In case it doesn't you need to set the environmental variable
export TERM=xterm-256color # or screen-256color
Ideally you'll want to add this to one of your shell configuration files (e.g.
echo "export TERM=xterm-256color" >> ~/.bashrc
If for whatever reason you cannot set the
TERM variable globally, it
is recommended to set an alias:
alias ghi='TERM=xterm-256color ghi'
ghi with full color support, but leaves the rest of your
Ubuntu users of a version prior to 12.04, beware! Your terminal will not
support 256 colors by default. You need to get an additional library
before before setting the
sudo apt-get install ncurses-term
Don't forget to reload your config file (e.g.
source ~/.bashrc) or
just reopen your terminal.
- What about cygwin‽
less can be problematic... you can use
git config --global ghi.pager "less -X -F -R"
- Can I have syntax highlighting of fenced code blocks?
Yes, you can - if you are using a terminal with 256 colors!
To enable this feature you just need to install the ruby wrapper for pygments:
gem install pygments.rb
Additionally you can specify the used colorset through your
git config --global ghi.highlight.style colorful
Fire up an
irb/pry session with the following to see a list of available
require 'pygments' Pygments.styles
- Can I use a custom $EDITOR for ghi?
You can define a custom editor by specifying
ghi.editor in your git
config (or export
$GHI_EDITOR in your environment).
git config --global ghi.editor vim
(The MIT License)
© 2009–2013 Stephen Celis (email@example.com). json-pure © Genki Takiuchi.
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.