i will not promote - Would you use a technical blogging platform where GitHub is the source of truth?

Would you use a blogging platform where GitHub is the source of truth? I'm thinking about building a publishing platform for technical blogs. The idea is that your articles stay as Markdown files in your own GitHub repo. You connect the repo, the platform finds the posts, and you choose which ones to publish. One thing I'd like to handle differently from the usual GitHub-to-blog setup is updates. A push wouldn't necessarily update the live article. The platform could keep track of the published commit and the latest commit separately, so you could preview or diff the changes before publishing them. Something like: published: a17c29f latest: bc832f1 [preview] [diff] [publish] Or you could put publish: auto in the frontmatter if you just want every push to go live. The repo would remain the source of truth. The platform would mostly handle rendering, search/discovery, SEO and custom domains. I know Hashnode already has GitHub publishing, so I'm not claiming the GitHub part itself is new. I'm more interested in whether treating Git revisions as part of the publishing workflow is actually useful. If you already write technical posts in Markdown/Git, I'd be interested in hearing: If you already write in Markdown/Git, what is still annoying about your publishing workflow? Is separating latest commit and published commit genuinely useful, or unnecessary complexity? Would you prefer publishing through frontmatter, a dashboard, or both? How important are private repos and repo-hosted assets? What would make you choose this over Hashnode or a static site? What would make you immediately reject it? I'm leaning towards Go + PostgreSQL for the backend and Next.js for the frontend.