Can I blog using GitHub issues on my phone? Let’s find out.

I’ve attached an image to this from my phone which should be used as the posts hero/featured image.

This is an experiment in using GitHub issues as a blogging platform. The beauty of this approach is that I can write blog posts directly from my phone using the GitHub mobile app, complete with images and rich text formatting.

Why GitHub Issues for Blogging?

Using GitHub issues for blogging offers several interesting advantages:

1. Mobile-first writing: I can write and publish blog posts directly from my phone using the GitHub app
2. Built-in discussions: Each blog post automatically becomes a place for comments and discussions
3. Version control: All blog content is version controlled by default
4. Markdown support: Rich text formatting with GitHub-flavored Markdown
5. Image uploads: Easy image attachments directly from mobile devices

The Process

The process is surprisingly simple:

1. Create a new issue in the repository
2. Write the blog post content in the issue description
3. Attach any images directly to the issue
4. The blog system automatically converts the issue into a blog post

This post itself was created from a GitHub issue, demonstrating the seamless integration between GitHub’s issue system and a static site generator.

Pretty cool, right? This opens up a whole new way of thinking about content management for static sites!

Update

The experiment was somewhat successful in that I could blog from github issues. However, there are limitations. The image can’t be moved directly from the issue into the repo (so no memeing from my phone, yet). What I didn’t expect was that copilot used a stock image in the repo for the hero. To add, I didn’t include the instructions in gh actions to post the content “as-is.” Instead, it heavily edited/added content past the first two sentences of the original post. I’ll work on it when I have time.