My blog (<a href="http://pwmckenna.net" rel="nofollow">http://pwmckenna.net</a>) is built on the same idea. The issue I ran into is that forks don't have their own issues, so its a bit harder to share than I originally thought (you need a seperate repo for the code, and for the issues).<p>Here's the source:
<a href="https://github.com/pwmckenna/til" rel="nofollow">https://github.com/pwmckenna/til</a>
So I'm trying to understand the benefits behind this as opposed to using a normal blog hosted with Github Pages? Then the posts would be visible in the repo.<p>If it is for having comments within a Github Pages blog, I found a solution that I wrote about myself about using a normal Jekyll hosted on GH Pages that pulls comments from Issues: <a href="http://seanlane.net/2016/Hosting_comments_within_issues_on_Github_Pages/" rel="nofollow">http://seanlane.net/2016/Hosting_comments_within_issues_on_G...</a>
Never considered using the issues for this. I did create a Jekyll plugin for using the wiki: Jekyll-Gollum (<a href="https://github.com/rubyworks/jekyll-gollum" rel="nofollow">https://github.com/rubyworks/jekyll-gollum</a>) Haven't messed with it in a while though, probably needs some love by now.
Did something similar about 10 months ago here <a href="https://github.com/formula1/NodeOS-Blog" rel="nofollow">https://github.com/formula1/NodeOS-Blog</a><p>I didn't realize hacker news had interest in these sorts of things, might have posted it
Neat! Though I think putting the content directly into the repository would be a better solution. I'd love to see more content systems use git (or something like git) for version tracking and publishing.