Skip to main content

Git sync for Help Center and API docs

Keep your guides and API documentation in Git, with changes synced to Featurebase. This would let your team maintain docs alongside your code, use AI coding tools to update them, and avoid copying changes between tools.

  • Connect your repository. Choose a GitHub repository, branch, and docs folder, including private repositories.

  • Sync your documentation. Bring across Markdown guides, API definitions, navigation, and images.

  • Edit in either place. Keep changes made in Featurebase and Git consistent through commits and pull requests.

  • Review before publishing. Preview changes before they go live, with clear sync status and errors when something needs attention.

  • Handle conflicts safely. Flag conflicting edits instead of silently overwriting changes, and respect branch protection rules.

GitHub would be the initial focus. Related requests include GitLab support, syncing multiple repositories, and choosing which files to include.

Post type
🔗 Integration
1 comment

Log in to comment and vote

Comments1

  • Mathias Jakob

    •

    Oct 6

    •

    Merged request

    •

    2 votes

    Git-based Help Center Management (Markdown Sync)

    I want to be able to manage Featurebase help center articles through a Git repository (e.g., GitHub). Specifically, I want to store articles as markdown files in a repo so that AI agents can read from and write to them, with changes syncing to Featurebase. This would allow for a cleaner integration with AI-driven documentation maintenance workflows.