Connect GitHub: Pull Requests for Posts and Site Fixes

Connect your site's GitHub repo and Revnu sends its changes as pull requests: new blog posts, and fixes to the site itself, such as copy, new pages or a fix from a site audit. You review each one and merge it when you're happy. Revnu never pushes to your main branch and never merges anything itself.

You need a GitHub account that can open pull requests on your site's repo. No repo, because your site is on a site builder? See My site has no code repo.

Connect your repo

1. 1

   Find GitHub in Connections

   Open Connections in the dashboard and find GitHub under Learn Your Business.

   Enlarge

2. 2

   Sign in to GitHub

   Press Connect and sign in with the GitHub account that has access to the repo. GitHub asks for two permissions. Both are explained below.

3. 3

   Choose the repo

   Press Choose Repo and pick your site's repo.

   If the picker says "No repositories found", see If it doesn't work.

4. 4

   Tell Revnu what to send as pull requests

   In chat, for example:

   Send each new blog post as a pull request to my repo.

   Make a pull request for the robots.txt fix from the audit.

5. 5

   Review and merge

   Revnu sends you the pull request link. Review it, ask for changes in chat if you want any, and merge it on GitHub. Your site's normal deploy puts it live.

What access Revnu asks for

GitHub's sign-in screen asks for two permissions:

• Repositories (repo). Read and write access to the repositories your account can reach, including private ones. GitHub has no narrower option for this kind of app. Revnu works only in the one repo you pick, and only on its own revnu/ branches.

• Your profile (read:user). Your GitHub name, so Revnu knows whose account it's using.

If that's more than you want to grant from your own account, connect a GitHub account that can only see the site's repo.

How it works

1. Revnu writes and fact-checks a post the same way it writes every post, or works out the site change you asked for.

2. For a post, it reads how your existing posts are stored: which folder they sit in, the file type, and the frontmatter fields at the top of each file. The new post follows the same pattern.

3. It creates a branch named revnu/ plus the topic, commits only the files the change needs, and opens a pull request that says what changed, why, and how to check it.

4. It sends you the pull request link.

The pull request comes from your own GitHub account, since Revnu uses the account you connected. Revnu keeps pull requests small and opens a few at a time, waiting for you to merge before it sends more. For a big change, such as rewriting a whole page, it checks the direction with you before it does the work.

How images get into a post

A hero image Revnu generates is hosted by Revnu, so a post can link to it by its web address rather than add a file to your repo. If your repo keeps images in a folder, say so in chat, for example "put images in public/blog and commit them with the post," and check the first pull request.

What Revnu sends as pull requests

• Blog posts, in your repo's format.

• Site copy, such as a clearer headline on the page that ranks for your name.

• New pages, such as a landing page or an FAQ.

• Conversion fixes, such as a broken link on your homepage, an error on your sign-up page, or a fix from a site audit.

• Ads tracking, when you ask: the Revnu Tag and the server call that reports sign-ups (event API), so ads can be judged on real outcomes.

It doesn't build product features, refactor your code or touch internal tooling. Growth from the outside is its job.

If your team uses a coding agent, it can review and merge Revnu's pull requests the same way it reviews a person's.

Rules Revnu follows in your repo

• It never pushes to main, not even a force push.

• It never merges its own pull requests.

• It changes only what the change needs. It doesn't refactor or tidy unrelated code.

My site has no code repo

Site builders such as ChatGPT Sites, Lovable, Framer and Wix keep your site inside the builder, not in a GitHub repo you can connect. Without a repo, Revnu can't edit your site at all. Here's what still works:

• Ask for paste-ready copy. Say "give me the exact copy changes and where to paste them in my builder." Revnu writes the text and tells you which page and section it goes in. You paste it, or paste it into the builder's own assistant.

• Publish posts on the hosted blog. Posts don't need a repo. The Revnu-hosted blog puts them on blog.yourdomain.com.

• Check whether your builder syncs to GitHub. Some builders, Lovable among them, can sync a project to a GitHub repo. If yours does, connect that repo here.

Once you've told Revnu you have no repo, it shouldn't keep asking you to connect one. If it does, say "I have no repo, give me copy to paste."

Good to know

• Say "merged" in chat once you've merged and deployed, so Revnu knows the post is live.

• The pull request is the post's record. Repo posts may not appear in Visibility > Posts, which lists hosted and Content API posts. Search Console is how Revnu sees their clicks.

• To change a merged post, ask Revnu for a new pull request with the edit.

• Ask for GitHub delivery in chat. The Posts setup screen offers the Content API instead.

If your site can fetch posts from the Content API, published posts and later edits reach your site without a merge each time.

If it doesn't work