Push MD – Git Sync for WordPress Content

FAQ

Is WordPress still the source of truth?

Yes. Your WordPress database remains authoritative. Git clients read and write through Push MD, so there is no separate content repository to reconcile.

Which content types are exported?

Posts, pages, supported block theme templates, template parts, navigation posts, read-only theme JSON context, Global Styles overlays, Gutenberg Guidelines when available, and built-in agent guidance.

Which branch should I use?

Use trunk. Push MD rejects pushes to other branches and rejects attempts to delete trunk.

Who can clone or pull?

Users must be authenticated and allowed to read the exported repository. Users with broad editorial access can clone the full export; otherwise every exported WordPress object must be readable to that user. This avoids exposing private, draft, pending, or future content through Git history.

Who can push changes?

Push MD checks permissions for each changed object. Updating, trashing, creating, publishing, scheduling, or making content private requires the matching WordPress capability.

What happens when someone edits in WP-Admin?

WP-Admin edits become Git-visible on pull. If a local checkout is stale, Push MD rejects the push before writing over newer WordPress content.

Do pushes create revisions?

Yes. Accepted content updates go through WordPress post APIs and create normal WordPress revisions.

How do agent skills become available?

Push MD stores agent skills as WordPress Guidelines. Today, that means the site needs the Gutenberg plugin installed and active, with the Guidelines experiment enabled from the Gutenberg Experiments page. After that, skills appear in the checkout under wp_guideline/skills/{slug}/SKILL.md, with generated aliases such as AGENTS.md for agent discovery.

Is this a static site generator?

No. Push MD gives you the local-file workflow people like in static site generators, while WordPress still handles previews, rendering, publishing, roles, and revisions.

Does Push MD sync my site to GitHub or another Git host?

No. Push MD makes WordPress itself behave like a Git remote for supported content. You can add GitHub, GitLab, Bitbucket, or another host as a separate remote in your local clone if your workflow needs that.

Does Push MD export plugin or theme source code?

No. The checkout is scoped to supported WordPress content. Theme-provided files such as wp_theme/{theme}/theme.json may appear as read-only context, but Push MD does not deploy theme or plugin code.

Does Push MD export media files?

No. Media mirroring is planned future work. The current release does not mirror uploads or import attachment binaries.

Does Push MD send site content to another service?

No. Push MD does not send content to GitHub, Automattic, WordPress.org, or any other third-party service. It exposes a Git endpoint on the WordPress site where the plugin is installed, and authenticated users connect directly to that site’s REST API.

Authorized clones can include supported content and prior Git revisions. Private, draft, pending, and future content may appear when the authenticated user is allowed to read the full export. Treat clone URLs, Application Passwords, and local clones as sensitive site access.

What happens when I uninstall Push MD?

Uninstalling Push MD removes its Git object-store database tables, seed progress options, transient import lock, and scheduled seed task. It does not delete WordPress posts, pages, templates, navigation posts, Global Styles, Guidelines, or other WordPress content.

The removed tables contain Push MD’s derived Git repository history. Reinstalling Push MD can seed a new repository from the current WordPress content, but it cannot restore the previous Push MD Git history unless you kept a clone or database backup.