Create Accountor Login
Docs

Keeping a Website in Step with 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 It Does

A website's Sources page keeps its pages in step with files in your own GitHub repository. Say which folder or file becomes pages, posts, or docs, see what would change, and press Sync Now. Every page it makes is a draft that waits for a person to publish it. Nothing goes live by itself, and nothing in GitHub is ever changed.

Sources is the plain way to do it. If you want your own steps (read a file, then do something with it), a workflow can do the same job: see Saving Website Pages From a Repository.

Connect GitHub

Sources reads your repository through your own GitHub connection. An owner or admin adds it in Settings, Connections, Connected Services, then Connect a Service, then GitHub, with a read only key for only the repositories you choose (see Reading GitHub From a Workflow). Sources uses that same connection, and the key is never shown again.

Add a Source and Its Mappings

Choose Add a Source on a website's Sources page (action sites.source.save). A website can have up to 10 sources. A source is one repository (from the ones your connection lists) and one branch, such as main, with up to 20 mappings. A new source is turned off.

Each mapping has:

  • Path. A folder (such as docs) or one file (such as about.md) in the repository. Leave it empty for the whole repository. Only Markdown and HTML files are read.
  • Becomes. Pages for now. Collections and data values come in a later update.
  • Bring In Pictures the Files Point At. On for a new mapping (see Pictures From GitHub below). A mapping made before this keeps it off until a person turns it on, so nothing changes by itself.
  • When It Goes Live. Keep as a Draft (the start) or Publish Automatically, set for this mapping alone (see Publish Automatically below).
  • Kind. Page, post, or doc. This is the default address the files follow: a doc lives under /docs/, a post under /blog/, and a page at its own address.
  • Address folder. An optional folder the pages go under. A mapping of handbook with the address folder handbook makes handbook/hours.md the page /handbook/hours. A file's own front matter address is used exactly as written.

A file docs/start.md in a mapping of docs with kind doc is the doc /docs/start. A file named index.md is its folder's own page. The same rules as the workflow steps apply: the title comes from the file's front matter or its first heading, Markdown becomes the website's own blocks, HTML is cleaned the same way as a custom section, and an address can use only lower case letters, digits, dashes, and slashes.

Several mappings in one source, and several sources on one website, are how you set up different groups: docs, a handbook, and posts each get their own folder and kind. Two mappings cannot use the same path.

Saving a mapping makes the next sync read every file again. Taking a mapping away hides it and keeps it, and the pages it made stay exactly as they are.

Pictures from GitHub

A Markdown or HTML file in a mapped folder can point at pictures in the same repository by a relative path, such as ![The Sources page](media/sources.png) or <img src="../images/flow.png" alt="A flow">. With Bring In Pictures the Files Point At on, a sync does this for each picture a file points at:

  • It finds the picture. The path is worked out from the file's own folder and must stay inside the repository (.. may go up, never out). An address that starts with http, //, or data:, a path through a symbolic link, and a path that is not there are left out, with the reason in the changes list.
  • It checks it like an upload. A PNG, JPEG, WebP, or GIF only, up to 5 MB and 50 megapixels. The type is read from the file's first bytes, never its name, so a script named .jpg and every SVG are refused (an SVG picture can carry code).
  • It keeps it with the website's pictures. The picture is stored in Files, encrypted like any file, in a folder named for the website, and added to the website's pictures. The same picture used by two pages is stored once.
  • It rewrites the reference. A Markdown picture becomes an image block where it stood in the text, with the description you wrote. An HTML picture keeps only its own address on the website and its description. The page never points at GitHub.
  • It remembers where it came from. A picture shows From GitHub with its file and the commit it came in at, on the Pictures list, and a managed page lists its pictures.

A picture with no description is left out, and the page still syncs. Add a description in your file, such as ![The Sources page](media/sources.png), so people who cannot see it know what it shows. A picture nothing points at is never read, and a script, stylesheet, font, PDF, or video is never brought in, even when a file points at it.

Pictures follow the rules of pages. A new or changed picture changes the page that shows it, so the page waits in the website's list of changes as a draft. A changed picture comes in as a new picture, and the earlier one stays stored. A picture file removed from GitHub keeps the picture and the page exactly as they are, and the people who manage Websites are told once. A sync never deletes a picture.

Limits: a picture is up to 5 MB and 50 megapixels, one sync brings in up to 100 pictures (a larger first sync is refused with the count, and you choose a smaller folder), a page shows up to 50, a website holds up to 2,000, and a repository can hold up to 5,000 picture files while a mapping brings pictures in.

See What Would Change

Preview (action sites.source.sync, preview) reads the branch and lists what a sync would add, change, or leave alone. It writes nothing: no page, no note, no kept file. It works while a source is off.

Sync Now

A person turns a source on with Turn On (action sites.source.set, needs the permission to publish a website), then presses Sync Now (action sites.source.sync). The work runs in the background, a few files at a time, and the page shows its progress.

  • Drafts. Each page is made or updated as a draft that waits in the website's list of changes. Nothing is made ready or published, unless a mapping is set to Publish Automatically (below).
  • Only what changed. A sync reads the branch's newest commit first. If it is the one already synced, it stops. Otherwise it reads only the files whose content changed since the last sync.
  • A page made by hand is never changed. If a file's address matches a page a person made, the file is refused, the page is kept exactly as it is, and the people who manage Websites are told on the bell and in Needs You Today, once for each file.
  • A removed file changes nothing. The file's page is marked as removed from GitHub, left exactly as it is (a live page stays live), and the people who manage Websites are told once. A sync never deletes a page.
  • Limits. A sync reads up to 500 files, each up to 200,000 characters of text, plus the pictures they point at (see Pictures From GitHub). A larger first sync is refused with the count, and you choose a smaller folder. A file that is not text, is too large, or makes an address that cannot be used is skipped with its reason. Two files that make the same address keep the first.

Publish Automatically

A mapping can be set to Publish Automatically instead of Keep as a Draft. Then a sync marks that mapping's changed pages ready and publishes the website, as the person who chose it and with their permission to publish (action sites.source.save). It is the same publish as the Publish button, so it publishes every ready page of the website, and Go Back in History returns to the version before.

  • A person's choice. Only a person who can publish a website chooses it. An assistant or key cannot, and one that is already on can only be kept or turned off. If the person later loses the permission to publish, the mapping goes back to drafts until someone with the permission chooses it again.
  • The first sync is always drafts. The first sync of a new mapping is saved as drafts whatever it says, so you see everything first. The next syncs follow its choice.
  • Never over an assistant's change. While a change an assistant saved is waiting for a person, nothing is published. The sync saves its changes as drafts and says why.
  • Never by an assistant. A sync an assistant starts always makes drafts.
  • A file that says ready: false at the top stays a draft.
  • Removed files change nothing. A file removed from GitHub never takes a live page offline, even with Publish Automatically. You decide.
  • What Changed shows which items went live, and the sync's message says which version was published.

Start It from GitHub or on a Schedule

A sync can start three ways: you press Sync Now, GitHub tells the website about a push, or a schedule is due. A source's What Starts a Sync block shows each.

  • A push to the branch. Make Address (action sites.source.hook.make, for owners, admins, and anyone whose role allows managing websites) makes the source's own address and a secret, shown once with a Copy button. In the repository on GitHub, open Settings, Webhooks, Add webhook, paste the address, set the content type to application/json, paste the secret, and choose just the push event. The address never changes for the life of the source. Replace Secret makes a new secret and the old one stops at once. Turn Off Address and Turn On Address (action sites.source.hook.set) stop and start deliveries. Address shows the address and the recent deliveries, with only their time and what happened (action sites.source.hook.show).
  • A schedule. Off at first. Choose Every Hour, Every 6 Hours, or Daily (action sites.source.schedule, for people who can publish a website). It never runs more often than every hour, and it stops when the source is turned off.

Each delivery is checked inside your account before anything is read: its signature (made with your secret), its size (1 MB at most), and its delivery id (a repeat is ignored). Thirty deliveries a minute are taken. Only a push to the source's branch in the source's repository counts; a ping, another branch, or a deleted branch is answered and dropped. A source that is off takes the delivery and drops it. A delivery only queues a sync and answers at once. Pushes close together become one sync of the newest commit, and a push that comes while a sync is running adds one more sync after it. A sync that finds the branch at the commit it already synced stops after one call to GitHub. Every sync a push or a schedule starts follows each mapping's own choice, drafts or Publish Automatically.

The body GitHub sends is read in memory and dropped. It is never kept or logged, and neither is your secret.

What Changed

Each preview and sync ends with a list (action sites.source.changes): the commit, then each item with Added, Changed, Removed, Skipped, or Refused, its address, its file, and a plain reason. It holds names and addresses, never the text of a file.

When Something Goes Wrong

The page says it in plain words: GitHub did not accept the key, the repository is not on your connection, the branch was not found, the repository is too large to read in one go, or GitHub is busy (it is tried three times, then stops and says so). Nothing is changed by a sync that stops.

Remove a Source

Remove (action sites.source.remove) hides a source and turns it off. It is kept, Bring Back returns it, and the pages it made stay exactly as they are.

Who Can Do It

  • Anyone who can see websites can see sources, syncs, and changes.
  • People who can build websites (the edit permission) add and change sources and mappings, press Preview and Sync Now, and remove a source.
  • People who can publish a website turn a source on or off.
  • Connecting GitHub is for owners and admins, in Settings, Connections.

For AI Agents

An assistant can list sources (sites.source.list), read the changes of a sync (sites.source.changes), save a source and its mappings (sites.source.save, always turned off), and queue a preview or a sync (sites.source.sync). A sync an assistant starts makes drafts only, whatever a mapping says. An assistant cannot choose Publish Automatically and cannot publish. An assistant cannot connect GitHub, make or replace a source's address or secret, turn a source or its address on, set a schedule, or remove a source.

What Is Kept

Counts, commit ids, file paths, page addresses, and plain reasons, in your own account. Never the text of a file and never your key. The pages a sync makes are ordinary pages of your website, kept in your account like any other, and included in Export Everything with your sources.

Ask Us Anything

We’d love to hear from you!