---
title: "GitHub sync (coming soon)"
description: "Keeping a guide's Markdown in a GitHub repository isn't available yet. What's planned, and what to do until then."
canonical_url: https://docs.markdrop.in/guides/github-sync
last_updated: 2026-10-31
prerequisites: [/guides/overview]
site: "Markdrop Docs"
index: https://docs.markdrop.in/llms.txt
---

# GitHub sync (coming soon)

> **Warning: Coming soon**
>
> GitHub sync isn't available yet. In the app, **Connect a GitHub repo** on the New guide form and **GitHub sync** in a guide's settings are marked **Coming soon**, and their buttons don't do anything yet.

![The Connect a GitHub repo option on the New guide form: the GitHub repository panel with a Coming soon badge and a disabled Connect GitHub button.](https://docs.markdrop.in/docs-assets/guides/repo-sync/repo-coming-soon.webp)

## What's planned

The app describes it like this:

- You pick a repository and a folder, and your Markdown stays in Git.
- Every push to the main branch publishes the guide.
- Pull requests get a preview link.
- Edits made in the browser come back as commits.

## Until then

- **Start blank or from a template**, and write in the [editor](https://docs.markdrop.in/guides/editor). Its **Markdown** mode shows each page as the Markdown file it is, front matter included, so you can paste in pages from a repository.
- **Coming from GitBook?** [Import the public site](https://docs.markdrop.in/guides/import-from-gitbook).
- **Want your pages in Git today?** The engine that builds Markdrop Guides can build a folder of Markdown files on your own server. It's early. See [Self-hosting](https://docs.markdrop.in/guides/self-hosting).