Pages Managed from GitHub
Part of the MountDev Ops Websites documentation. Updated November 17, 2026
MountDev Ops Websites documentation | Updated November 17, 2026
Our Commitment
MountDev Ops is built security first. Your business data belongs to you, and you can export all of it at any time. We never use analytics or tracking of any kind inside MountDev Ops.
Every update passes all 6,565 automated checks before it ships, and every screen change is walked through before release.
What a Managed Page Is
A page, post, or doc that a sync of a GitHub source made (see Keeping a Website in Step With GitHub), or that a workflow saved from a file in your repository, is managed from GitHub. Its words live in the file in GitHub. The next sync would put the file's words back, so changing the page here would be lost.
A managed page shows:
- A From GitHub pill on its row in Pages (and File Removed From GitHub when its file is gone).
- A Managed by GitHub card at the top of the page builder with the file, the repository, the commit it was last synced from, and when. Open in GitHub opens the file in a new tab.
- Editing is turned off in the builder. A change saved another way is refused with: "This page comes from docs/pricing.md on GitHub. Change it there, and Sync Now brings it in. Or choose Stop Managing to edit it here."
Its status still works here: a person can mark a managed draft ready, and publishing works as it does for any page. Preview and History work too.
Stop Managing
Stop Managing (action sites.page.unmanage) turns a managed page into a page made by hand. Nothing on the page changes. A later sync will not change it: if its file changes, the file is refused, the page is kept, and the people who manage Websites are told. People who can build websites do this, after a confirmation. An assistant or key cannot.
To manage a page from GitHub again, remove the page and sync.
For AI Agents
Pages an assistant reads (sites.page.list and sites.page.get) say whether each is managed and where it came from:
managed: true or false.source: the repository and the file path in it, for a managed page.synced: the commit the page was last synced from and when.source_removed: true when its file is gone from GitHub.
An assistant that wants to change a managed page changes the file in GitHub, not the page. An assistant cannot stop managing a page. A change it tries on a managed page is refused with the sentence above.
What Is Kept
The repository, the file path, the commit id, and the time of the last sync, with the page, in your own account. Never the text of a file other than what is on the page itself.
Pictures on a Managed Page
A page that shows pictures brought in from GitHub lists them on its Managed by GitHub card, each with its file and the commit it came in at. A picture is changed in GitHub too: change the file there and Sync Now brings in the new picture, and the page waits in the website's list of changes. If a picture file is removed from GitHub, the picture and the page are left exactly as they are, the card says the file was removed, and the people who manage Websites are told once. See Pictures From GitHub.
