Two-way, not one-way
Edit in Git or in the editor, and doxbrix reconciles both directions so neither side goes stale.
Git Sync · Docs-as-code
Your repo and your docs, finally in sync
Two-way sync with GitHub and GitLab. Engineers ship docs in pull requests, writers publish in the editor, and every change flows both ways, conflict-aware and review-safe.
Two-way GitHub & GitLab Conflict-aware Review before publish
How it works
Docs that move with your code
Connect once, then let changes flow both ways without copy-paste release rituals.
1. Connect your repoLink a GitHub or GitLab repository in a few clicks.
2. Map docs to projectsPoint repository folders at projects and spaces.
3. Review every changePreview diffs and resolve conflicts before anything goes live.
4. Publish in syncApproved changes flow to your branded help center automatically.
Built for real teams
Docs-as-code, without the chaos
Keep engineering velocity and editorial control at the same time.
Conflict-aware by design
Pick a conflict policy, preview changes, and avoid surprise overwrites between your repo and your docs.
AI-ready after every sync
Synced content is immediately indexed for semantic search and grounded, cited AI answers.
FAQ
Common questions
Does it work with both GitHub and GitLab?
Yes. doxbrix supports two-way sync with both GitHub and GitLab repositories, including self-managed GitLab.
What happens when there is a conflict?
You choose a conflict policy. With “Git wins”, the repository is the source of truth; in review mode, conflicting changes are held for a person to resolve before publishing.
Can non-developers still edit docs?
Absolutely. Writers and support teammates edit in the doxbrix editor with approvals and version history, while engineers keep working in pull requests. Both sides stay reconciled.
Is synced content searchable and answerable by AI?
Yes. After every sync, approved content is indexed for semantic search and grounded, cited AI answers, with no extra step.