MAmaelkum·Jul 9, 2018
In a true hackerish style, I rolled my own solution: https://github.com/marekjm/issue
Back in 2015, I decided that all the issue tracking systems I knew are too heavy-weight. I don't need kanban, agile, or any other buzz - I just need a simple tool to track my issues. I had several requirements: 1/ it must work off-line,
2/ it must be distrubuted (to allow many people working simultaneously on their off-line clones),
3/ it must work in command line,
4/ it must provide minimum distraction,
5/ it must allow me to tag, and search the issues,
and I worked from there.
fast forward to 2018 ...and I'm still using it. It does the job for my Free Software projects, and helps me at work (tested in three companies already). It is definitely not bug-free (but the risk of data-loss should be low), and the installation must be done manually from GitHub
Read the rest
, but it Works For Me (tm) ;-)
Sample workflow:
$ issue open "OH noes, a bug"
$ issue ls --open
deadbeef OH noes, a bug
$ issue slug --git-checkout --git-branch --git deadbeef # or just issue sl -gBC de
...hack, hack hack...
$ git commit -am "Fix"
$ issue close -g HEAD de
$ git checkout master
$ git merge -
By using the `-` as the placeholder for "last active issue" I can make this sequence even shorter. Minimal distraction, no switching between the terminal and the browser, no waiting for slow Web interfaces.
/end of shameless plug