Sync with GitHub
How to Set Up Bi-Directional Sync with GitHub
Prerequisites
- You will need a GitHub account.
- When syncing to a repository in an organization, you will need permission to create an empty repository.
Set Up
- Navigate to Settings > Git Connection page.
- Select GitHub.
- If you haven’t already, create an empty repository in GitHub—make sure to uncheck the option to create a README.
- Sync with your provider and authenticate. Grant access to the repository you’d like to sync with and confirm your repository on the next screen.
Changing Repositories
- Within ReadMe, disconnect the project via the trash icon.
- Within GitHub, create your new repository (must be empty).
- Navigate to Applications > Installed GitHub Apps.
- Find ReadMe Sync and click Configure.
- Under Repository access, select the new repository you’d like to sync to.
- Return to ReadMe and connect to your new repository.
Editing Your Docs
- The initial commit from ReadMe is to establish branch synchronization with GitHub
- Branch names must exactly match the version names defined in ReadMe
- Any mismatched version and names will exist in GitHub and will not sync with ReadMe.
GitHub Enterprise Server
If you’re using a self-hosted GitHub Enterprise Server (GHES), you can set up syncing from your Group dashboard under Git Connection. Syncing requires a new, empty repository, and each child project can only sync to one repository.
If GHES isn’t available for your project, please contact your Customer Success Manager.
GitHub Branch Protection
If your GitHub repository uses branch protection rules, you’ll need to configure them to allow the ReadMe Sync app to push changes. Here's how to set it up based on your GitHub configuration:
For GitHub Rulesets (New Version)
- Navigate to your repository’s branch protection settings.
- Under the Bypass list section,+ Add bypass.
- Search for ReadMe Sync (App • readmeio) and set the permission to Always allow.

Adding ReadMe Sync to the GitHub Rulesets bypass list for direct push access.
For Legacy Branch Protection
- Go to your repository’s branch protection rules.
- Find the Allow specified actors to bypass required pull requests section.
- Add readme-sync (ReadMe Sync) to the allowed actors list.

Configuring ReadMe Sync in legacy branch protection settings to bypass pull request requirements.
This configuration ensures that changes made in ReadMe’s editor can be synchronized to protected branches in your GitHub repository.
FAQ
How does ReadMe integrate with GitHub and what permissions are required?
ReadMe uses a GitHub App with rep-level access: read-only for metadata(required) and read/write for syncing content. Webhooks handle syncs, change detection, and conflict resolution.
Why don't my branches show on GitHub?
New branches you create after enabling bi-directional sync automatically creates a corresponding branch on Github, but existing branches will not create a corresponding branch on GitHub until you save a change (however small) to that branch on the ReadMe side.
Updated about 14 hours ago