Alternatives¶
Before diving in and spitting out this package I looked at the alternatives below. If I have missed something please drop me a mail.
Both the ghi
and github-cli
packages listed below are very useful, and
quite usable, clients for GitHub issues. You should definitely try them out
before making a decision on what to use, and this would also allow you to
highlight any possible bias I may have shown in comparing them ;)
ghi
¶
ghi is a great issues client, written in Ruby.
I personally didn’t like the “feel” of the command line interface, and wanted slightly different output.
hubugs
provides the following advantages:
Easily customisable output
On-disk cache support
and has the following disadvantages:
hubugs
requires a significant number of external packages, which may be a problem for some users
github-cli
¶
github-cli is a fantastic command-line client for GitHub’s issues, written in
Python. I really liked github-cli
to the extent of authoring a few
patches, but just didn’t find it comfortable to use in the long run 1.
hubugs
provides the following advantages:
Easily customisable output
HTTP compression support
On-disk cache support
Pull request integration
Uses the same method as
git
for choosing an editor to use, which will only affect you if you a custom editor for interacting withgit
and has the following disadvantages:
hubugs
requires a significant number of external packages, which may be a problem for some users
- 1
If you look at the timeline for the hubugs repository and my github-cli fork you’ll see I was using
github-cli
for a few months after spikinghubugs
.