Re:GitHub was down
by apendleton on Tuesday June 11, 2013 @10:37PM
(#5866158)
I've been telling people for a fair while that I wish Github issues were stored as part of the git repos themselves, not so much for availability reasons as that it'd be awesome if the state of bugs got branched and merged along with everything else, so that a bug could be fixed in a branch, but not yet in master, and would get fixed in master when the branch got merged. But I guess availability would be a nice additional perk.
[ Parent
| on HN ]
Re:GitHub was down
by merlincorey on Tuesday June 11, 2013 @10:43PM
(#5866190)
You're welcome: http://bugseverywhere.org/
Re:GitHub was down
by apendleton on Tuesday June 11, 2013 @10:51PM
(#5866227)
Wow, slick. Thanks for sharing.
If you use the "fixes #7" syntax in a branch commit, the issues will be closed only when that branch is merged to your default branch (usually master). I realize that this is only part of what you desire, but it's a useful recent addition: https://github.com/blog/1386-closing-issues-via-commit-messa...
What I would like to see is an analogue to offlineimap for GitHub's project management services.
The protocol could even be email based.
e.g. a pull request is an email with the git formatted patch attached. Issues are emails with discussions as threaded mail/news, etc.