If you built your site with an AI coding tool or a framework like Astro, Next.js, or Hugo, your blog posts probably live as files in a GitHub repository instead of a CMS. The Git integration lets RightBlogger publish straight into that repository. Each new post is committed in the same format as your existing posts, and your host (Vercel, Netlify, Cloudflare, or another) builds and deploys it like any other change.

It also works with Cloudflare Artifacts repositories, and Site Agent can improve the posts already in your repository.

What You Need

  • A GitHub or Cloudflare Artifacts repository that your site builds its blog from: a folder of Markdown or MDX posts with frontmatter, or one JSON file that holds every post.
  • A host that deploys your site when the repository changes.
  • For GitHub, permission to install a GitHub app on the account or organization that owns the repository. If you can’t, a fine-grained access token works too.

Connect Your Repository

  1. Pick your site in the site picker at the top of the sidebar, or choose Add Project to create one. Integrations are set up per project.
  2. Click Settings at the bottom of the sidebar, choose Integrations, and click Git.
  3. Choose Continue with GitHub. GitHub asks which repositories to share with RightBlogger. Pick only the one your site builds from.
  4. Back in RightBlogger, choose that repository from the GitHub repository list. RightBlogger reads it and checks that it can push to it, which takes a few seconds.
  5. Check what it found. You will see how many posts it found and where, plus a link to your newest post. If the Posts location, Site URL, or Post URL pattern is wrong, fix it or click Detect these again.
  6. Choose your publishing settings (below), then save the project.

Connect With an Access Token Instead

Choose Use a GitHub access token or Continue with Cloudflare Artifacts, paste the repository URL, then paste a token:

  • GitHub: a fine-grained personal access token limited to that one repository, with Contents set to Read and write. Add Pull requests (Read and write) if you want to review posts before they go live.
  • Cloudflare Artifacts: an API token from My Profile → API Tokens with the Artifacts Read and Artifacts Edit permissions. A repo token from the Artifacts Tokens tab won’t work, because it only allows git pushes.

Tokens are stored encrypted and never shown again. To replace one, paste a new token and click Check again.

Publishing Settings

  • Commit to the production branch. Off by default on GitHub: each post opens as a pull request for you to review and merge, so nothing reaches your live site until you merge it. Hosts with preview builds give each pull request a preview URL. Turn it on and each post is committed to the branch your site deploys from, going live on the next build. On Cloudflare Artifacts this is on by default. Turning it off puts each post on its own rightblogger/<slug> branch for you to merge with git.
  • AI featured image. Generates a unique image for each post. If your repository keeps its own images, the image is committed next to them. Stock photos stay linked, as their licenses require.
  • Advanced. Set the Production branch if it isn’t the repository default. On GitHub, set Commit author email if your site deploys on Vercel, since Vercel only deploys commits from an email on your team. Add Pages the Site Agent skips for pages a script regenerates.

Send Posts to Your Repository

Create an article in RightBlogger, click Send To, and choose Git. Each post is one commit that adds the post and its images. Nothing else in your repository changes.

New posts copy the fields of your newest post, so they match whatever your site expects (tags, author, layout, and so on). Dates are written in the same format, and things specific to that older post, like its slug or canonical URL, are left out.

To publish on a schedule, use Automations: queue topics in the Content Planner, pick your dates, and RightBlogger writes and commits each article on its day.

When Posts Go Live

A commit is not a deploy: your post goes live when your host finishes building the change. RightBlogger holds social posts until your host has had time to build, so shares never point at a missing page. It then checks that the post reached your live site, and asks your host to build again if it didn’t.

On Cloudflare Artifacts, posts go live when Workers Builds deploys the repository (your Worker in Cloudflare, then Settings → Builds).

Site Agent on Git Sites

Site Agent works with Git-connected sites. It reads the posts in your repository, finds improvements like internal links, sharper meta titles and descriptions, and clearer sentences, and commits the ones you approve. In Smart mode, safe changes apply on their own.

  • Changes made close together land in one commit, so your host builds once.
  • Site Agent commits its edits to your production branch, even if new posts use pull requests.
  • On Markdown posts, an edit that can’t be matched cleanly to the file is skipped instead of reformatting the whole post.
  • Every applied change can be undone for 30 days from the Recently applied card, which commits the original file back.

Learn Your Product From the Same Repository

If your site is for a product (a SaaS app, a tool, a plugin), you can also connect the same repository as knowledge. RightBlogger learns your product from your PRODUCT.md guide, README, docs, and changelog, and when an article covers or mentions a feature, the article writer and Autoblogging can check how it actually works. See Learn From Your Repository.

Frequently Asked Questions

Which site frameworks work?

Any site that builds its blog from Markdown or MDX files with frontmatter, or from a JSON content file: Astro, Next.js, Hugo, Eleventy, Jekyll, and similar. Folder-per-post layouts (like my-post/index.md) and dated file names (like 2026-10-19-my-post.md) are kept as your site uses them.

Does RightBlogger clone my repository?

No. It reads only the files it needs through GitHub or Cloudflare, and each publish pushes only the new files.

What can the GitHub app access?

Only the repositories you pick, with Contents and Pull requests set to Read and write. Each publish uses a short-lived token for that one repository. You can add or remove repositories anytime from Add repositories on GitHub in the Git integration.

My post was committed but never showed up on Vercel. Why?

Vercel only deploys commits from an email on your Vercel team. Open the Git integration, expand Advanced, and set Commit author email to the email you use on Vercel.

Can I use more than one repository?

Each project connects to one repository. To publish to another site, create a separate project for it.