Hacker News new | ask | show | jobs
by reycharles 4639 days ago
The github issue tracker and wiki is not distributed as far as I know, though.
2 comments
josegonzalez 4639 days ago
The wiki is a git repository, so in effect it is distributed.

The issue tracker is not, unfortunately, but neither are most issue trackers.

link
tenfingers 4638 days ago
The solution is to use a bug tracker within the SCM:

http://bugseverywhere.org/ (my personal favorite, but there are 3/4 other options that you can look into).

Not only it does offer distributed bug tracking on the command line (without breaking your workflow), but it implicitly allows to isolate bugs to branches. You can fix a bug in a branch, and a subsequent merge of the changeset will automatically fix the current branch.

I don't understand why these projects are so underrated. In "early git times", distributed bug tracking on top of git was quite a hot subject. They solve many issues nicely.

Github might be a "nifty" viewer, and I do host projects on github for added visibility (by simply using a second push remote), but that's about it. I find "tig" and "bugseverywhere" to complement git nicely and work much better than any web browser could.

link
bscofield 4639 days ago
Sure, but that's not the point of this gem. This just allows deploys to continue when GH is unavailable.
link