Overview
Connect any GitHub repo to your Docsio site. Edits in Docsio commit to your branch when you publish; pushes to your branch from anywhere else rebuild your site automatically. Free on every plan.
What you get
- One-click connect. No GitHub Actions to set up, no CI yaml to maintain — Docsio is the build pipeline.
- Two-way sync. Edits in Docsio commit to your branch on Publish. Pushes to your branch rebuild your site in ~60 seconds.
- Editor + AI agent stay fully enabled. Unlike other tools that lock the editor when sync is on, Docsio keeps both interfaces working. Use whichever fits the moment.
- Only your content commits. Markdown pages, sidebar metadata, uploaded images, and a small config file. The rendering engine and any internal Docsio state stay on our side — your repo stays clean.
- No data loss. If a teammate pushes to git while you have unpublished editor changes, Docsio snapshots your draft before applying the pull. One-click recovery.
When to use it
- Engineers prefer their IDE. Some of your team would rather write markdown in VS Code than in a web editor.
- You want git history. Every edit becomes a commit. Real audit trail.
- You're migrating from another tool. Mintlify or GitBook users moving to Docsio can keep their existing repo.
- You want code reviews on docs. PRs before merge, the same way you do code reviews.
When to skip it
- You're a solo doc author who likes the visual editor.
- You don't have a git workflow to integrate with.
- Your docs change rarely — the editor alone is plenty.
You can connect later. Sync is fully optional.
Quick path
- Project settings → GitHub → Connect GitHub.
- Install the Docsio Docs Sync app on your repo (you grant per-repo access).
- Pick org / repo / branch / direction (pull or push for first sync).
- Click Save.
Detailed walkthrough in Connect a repo.
How sync direction works
On the first sync, you pick a direction:
- GitHub → Docsio. Pull existing markdown from the repo into your Docsio site. Use this when your repo already has docs content.
- Docsio → GitHub. Push your current Docsio content into the repo as the seed commit. Use this when the repo is empty (or you want to start from a Docsio-built docs site and use git going forward).
After the first sync, both directions are live automatically — you don't pick again.