[bscofield]

I'm surprised there's only one "git is distributed" comment thread so far, but as a reminder: http://rubygems.org/gems/deus_ex may help with getting deploys running during a GitHub outage. Usage instructions are at http://rubydoc.info/gems/deus_ex/0.0.2/frames.

[reycharles]

The github issue tracker and wiki is not distributed as far as I know, though.

[josegonzalez]

The wiki is a git repository, so in effect it is distributed.

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

[tenfingers]

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.

[bscofield]

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