// the find
yihong0618/gitblog
People Die, but Long Live GitHub
A personal blog by yihong0618 built entirely on GitHub Issues as the CMS, with GitHub Actions rendering each issue into a static Astro site and generating an RSS feed. It's aimed at developers who want to blog without standing up a server, database, or markdown-file workflow — just open an issue and the pipeline handles the rest.
Writing a post is literally opening a GitHub issue, so it works from the GitHub mobile app, web UI, or API with zero local tooling. The build pipeline (generate_site.yml) is fully automated: pull issues, render to Astro, deploy, no server to babysit. It even ships a dedicated RSS stability check script (check_rss_stability.mjs), which most issues-as-blog projects skip validating. 1.6k stars and 142 forks show the pattern has actually been adopted as a template by other people, not just used by the author.
This is the author's personal blog repo with the plumbing attached, not a packaged tool — forking it means inheriting years of yihong0618's own diary entries (hundreds of files under BACKUP/) that you'd have to strip out before it's usable as your own blog. There's no setup documentation at all; the README is 100% about the author's content, so adapting main.py and the Actions workflow for yourself means reading the source directly. The data model is hard-locked to GitHub Issues, so no drafts, no scheduling, and your blog's availability depends on GitHub Pages/Actions staying up. The BACKUP/ folder also has near-duplicate filenames for the same post (slightly different titles/punctuation), a sign the archival step isn't fully clean.