4 ms·
A lot of people rely on other features of GitHub for their workflow: issues, pull requests, comments.
by dan_manges 13y ago
A lot of people rely on other features of GitHub for their workflow: issues, pull requests, comments.
- apendleton 13y agoI'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.
- merlincorey 13y agoYou're welcome: http://bugseverywhere.org/ http://bugseverywhere.org/
- apendleton 13y agoWow, slick. Thanks for sharing.
- edhebert 13y agoWhat 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.
- j-kidd 13y agoThat sounds a lot like Linux kernel development.
- thedaniel 13y agoIf 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-messages https://github.com/blog/1386-closing-issues-via-commit-messa...