PushPull stores selected WordPress content in a Git repository using a canonical JSON representation instead of raw database dumps.<\/p>\n\n
This is a beta plugin. It is still under active development, has limited functionality, and currently supports only a narrow subset of the intended PushPull feature set.<\/p>\n\n
The current release supports these managed domains:<\/p>\n\n
PushPull keeps a local Git-like repository inside WordPress database tables and supports the following workflow directly from WordPress admin:<\/p>\n\n
The plugin also includes:<\/p>\n\n
This is an early, focused release. At the moment, PushPull is intentionally limited to:<\/p>\n\n
attachment.json<\/code> and the binary file<\/li>\n- Explicit opt-in attachment sync through a media-library checkbox<\/li>\n
- Overlay domains that scope themselves to enabled compatible base domains rather than exporting every backend row blindly<\/li>\n<\/ol>\n\n
It does not yet manage forms, arbitrary wp_options<\/code>, or arbitrary plugin data.<\/p>\n\nHow PushPull represents content<\/h3>\n\n
PushPull does not use WordPress post IDs as repository identity.<\/p>\n\n
For the currently supported managed sets it stores:<\/p>\n\n
\n- One canonical JSON file per managed item<\/li>\n
- One separate
manifest.json<\/code> file for manifest-backed sets that preserves logical ordering<\/li>\n- One directory per attachment for the attachments set, containing
attachment.json<\/code> and the binary file<\/li>\n- Stable logical keys instead of environment-specific database IDs<\/li>\n
- Canonical logical-key references for cross-domain relationships such as reading settings, translation groups, media folders, GeneratePress condition targets, and menu object references<\/li>\n
- Recursive placeholder normalization for current-site absolute URLs in post-type-backed content<\/li>\n<\/ol>\n\n
Configuration<\/h3>\n\n
PushPull currently supports GitHub and GitLab repositories.<\/p>\n\n
For GitHub, grant:<\/p>\n\n
\n- Repository metadata read access<\/li>\n
- Repository contents read and write access<\/li>\n<\/ol>\n\n
For GitLab fine-grained personal access tokens, grant:<\/p>\n\n
\nProject: Read<\/code><\/li>\nBranch: Read<\/code><\/li>\nCommit: Read<\/code><\/li>\nCommit: Create<\/code><\/li>\nRepository: Read<\/code><\/li>\n<\/ol>\n\nIn PushPull > Settings:<\/p>\n\n
\n- Select
GitHub<\/code> or GitLab<\/code> as the provider<\/li>\n- Enter the repository owner and repository name<\/li>\n
- Enter the target branch<\/li>\n
- Enter the API token<\/li>\n
- Enable one or more managed content domains in the managed content settings<\/li>\n
- Click
Test connection<\/code><\/li>\n- Save the settings<\/li>\n<\/ol>\n\n
Workflow<\/h4>\n\n
The normal workflow is:<\/p>\n\n
\nCommit<\/code> to snapshot the current live managed-set content into the local repository<\/li>\nFetch<\/code> to import the current remote branch into refs\/remotes\/origin\/<branch><\/code><\/li>\n- Inspect the live\/local and local\/remote diff views if needed<\/li>\n
Pull<\/code> for the common fetch + merge flow, or Merge<\/code> manually after fetch when you want review first<\/li>\nApply repo to WordPress<\/code> when you want the local branch state written back into WordPress<\/li>\nPush<\/code> when you want local commits published to GitHub or GitLab<\/li>\n<\/ol>\n\nIf both local and remote changed, PushPull can persist conflicts, let you resolve them in the admin UI, and then finalize a merge commit.<\/p>\n\n
When pushing to GitLab, PushPull currently linearizes local merge results into a normal commit on the remote branch instead of preserving merge topology. The merged tree content is preserved; only the remote Git history shape is flattened.<\/p>\n\n
Empty repositories<\/h4>\n\n
If the configured GitHub or GitLab repository exists but has no commits yet, Test connection<\/code> will report that the repository is reachable but empty.<\/p>\n\nIn that case, click Initialize remote repository<\/code>. PushPull will:<\/p>\n\n\n- create the first commit on the configured branch<\/li>\n
- fetch that initial commit into the local remote-tracking ref<\/li>\n
- make the repository ready for normal commit, fetch, merge, apply, and push workflows<\/li>\n<\/ol>\n\n
You do not need to create the first commit manually on the provider before using PushPull.<\/p>\n\n
TODO<\/h3>\n\n\n- Cache the admin-bar PushPull status summary so the high-level live\/local and local\/remote aggregation is not recomputed on every page view.<\/li>\n
- Move chunked async provider resumability fully into the provider layer so
AsyncBranchOperationRunner<\/code> no longer needs provider-specific GitLab staging rehydration logic.<\/li>\n- Improve push progress and recap reporting to distinguish newly uploaded objects from objects reused from the remote history.<\/li>\n
- Surface unresolved logical-reference mapping issues, such as GeneratePress condition IDs that could not be converted to logical placeholders, instead of silently leaving mixed raw IDs and canonical refs.<\/li>\n<\/ol>\n\n
External services<\/h3>\n\n
PushPull connects to the GitHub or GitLab API for the repository you configure in the plugin settings.<\/p>\n\n
The plugin uses the provider REST API to:<\/p>\n\n
\n- Read repository metadata and the default branch<\/li>\n
- Read and update branch refs<\/li>\n
- Read and create Git objects or provider-equivalent commit actions<\/li>\n
- Test repository access before sync operations<\/li>\n<\/ol>\n\n
PushPull sends the following information to the configured provider over HTTPS:<\/p>\n\n
\n- The repository owner, repository name, branch, and API base URL<\/li>\n
- Your configured API token in the provider-specific authentication header<\/li>\n
- Canonical JSON representations of the managed content you choose to commit and push<\/li>\n
- Commit metadata such as commit messages and, if configured, author name and email<\/li>\n<\/ol>\n\n
In the current release, the managed content sent to the provider is limited to the enabled supported domains: GenerateBlocks Global Styles, GenerateBlocks Conditions, WordPress Block Patterns, WordPress Menus, WordPress Pages, WordPress Posts, WordPress Custom CSS, GeneratePress Elements, explicitly opted-in WordPress Attachments, WordPress core configuration, WPML-backed translation management, and Real Media Library-backed media organization.<\/p>\n\n
PushPull does not send your whole WordPress database to the provider. It only sends the managed content represented by the enabled adapters.<\/p>\n\n
GitHub terms of service: https:\/\/docs.github.com\/en\/site-policy\/github-terms\/github-terms-of-service\nGitHub privacy statement: https:\/\/docs.github.com\/en\/site-policy\/privacy-policies\/github-general-privacy-statement\nGitLab terms: https:\/\/about.gitlab.com\/terms\/\nGitLab privacy statement: https:\/\/about.gitlab.com\/privacy\/<\/p>\n\n\n
Uploading in WordPress Dashboard<\/h4>\n\n\n- Download the plugin ZIP.<\/li>\n
- In WordPress, go to Plugins > Add New Plugin.<\/li>\n
- Click Upload Plugin.<\/li>\n
- Select the ZIP file.<\/li>\n
- Install and activate the plugin.<\/li>\n<\/ol>\n\n
Installing from source<\/h4>\n\n\n- Clone this repository into
wp-content\/plugins\/pushpull<\/code>.<\/li>\n- Run
composer install<\/code>.<\/li>\n- Activate PushPull in WordPress.<\/li>\n<\/ol>\n\n\n
0.0.15<\/h4>\n\n\n- Added a new primary
wordpress_menus<\/code> domain with canonical JSON export and apply for WordPress menus.<\/li>\n- Added v1 menu location support so theme menu assignments round-trip alongside menu structure.<\/li>\n
- Added canonical menu item references for pages, posts, taxonomies, post-type archives, and custom links, with hierarchy preserved through
parentItemKey<\/code>.<\/li>\n- Added focused menu export\/apply coverage and nav-menu bootstrap support in the test suite.<\/li>\n
- Updated the readme functionality description so WordPress menus are listed as a supported primary domain.<\/li>\n<\/ol>\n\n
0.0.14<\/h4>\n\n\n- Added a new
media_organization<\/code> overlay domain with a first Real Media Library-backed adapter that stores canonical attachment-to-folder path assignments instead of plugin-specific folder IDs.<\/li>\n- Expanded
WordPress core configuration<\/code> with wordpress_permalink_settings<\/code> support for the site's permalink structure.<\/li>\n- Added a PushPull status dropdown in the WordPress admin bar with high-level live vs local and local vs remote summaries plus quick links into Managed Content and the Audit Log.<\/li>\n
- Extended the WordPress pages and posts domains to own GeneratePress layout override meta, including legacy page-editor keys used for sidebar layout, footer widgets, full-width content, and disabled elements.<\/li>\n
- Hardened the admin and provider integration edges with safer admin-bar status fallback behavior and PHPStan bootstrap stubs for Real Media Library functions.<\/li>\n<\/ol>\n\n
0.0.13<\/h4>\n\n\n- Added a first core config domain,
WordPress core configuration<\/code>, with wordpress_reading_settings<\/code> support for show_on_front<\/code>, page_on_front<\/code>, and page_for_posts<\/code>.<\/li>\n- Added canonical page logical-key references for reading settings so front-page and posts-page options can round-trip across environments without leaking WordPress IDs.<\/li>\n
- Added a dedicated config-domain apply path so non-post WordPress configuration can be applied cleanly without pretending to be posts or overlays.<\/li>\n
- Introduced
Config domains<\/code> as a separate UI family alongside Primary domains<\/code> and Overlay domains<\/code> in settings and Managed Content.<\/li>\n- Changed the Managed Content screen to show only enabled domains, so disabled managed sets no longer clutter the tabs or overview.<\/li>\n<\/ol>\n\n
0.0.12<\/h4>\n\n\n- Added a new
translation_management<\/code> overlay domain with a first WPML-backed implementation that exports only in-scope translation groups for managed content.<\/li>\n- Added generic overlay-domain support, including separate
Primary domains<\/code> and Overlay domains<\/code> sections in settings and clearer visual separation in the Managed Content UI.<\/li>\n- Added managed-set dependency ordering so hard domain dependencies can be declared explicitly, with GeneratePress elements now ordered after WordPress pages and posts.<\/li>\n
- Added canonical logical-key mapping for GeneratePress element page\/post conditions so environment-specific object IDs no longer leak across sites.<\/li>\n
- Added the first overlay-specific apply path so non-post domains like translation management can be applied asynchronously without pretending to be WordPress posts.<\/li>\n<\/ol>\n\n
0.0.11<\/h4>\n\n\n- Added new managed content domains for WordPress posts and GeneratePress elements.<\/li>\n
- Added asynchronous, chunked
Apply repo to WordPress<\/code> operations with modal progress so large apply actions no longer rely on one long blocking request.<\/li>\n- Moved
Pull<\/code>, Fetch<\/code>, and Push<\/code> to the top Managed Content navigation row so branch actions stay available while working inside a specific managed set.<\/li>\n- Fixed GitLab recursive tree fetching so repositories with more than one page of files no longer silently miss later entries during fetch.<\/li>\n
- Improved attachment apply so WordPress regenerates target-side attachment metadata and image sub-sizes instead of reusing stale source-site thumbnail metadata.<\/li>\n<\/ol>\n\n
0.0.10<\/h4>\n\n\n- Added a GitLab provider with project, branch, commit, tree, and blob support plus linearized push support for merge results.<\/li>\n
- Added GitLab-specific settings and documentation, including fine-grained PAT permission guidance and a note that remote merge topology is flattened on push.<\/li>\n
- Fixed GitLab push ref tracking so follow-up commits and pushes no longer fail after the first successful push.<\/li>\n
- Fixed chunked GitLab fetch and pull so synthetic root trees survive across async requests.<\/li>\n
- Fixed chunked GitLab push so staged synthetic blobs, trees, and commits are restored correctly across async requests.<\/li>\n<\/ol>\n\n
0.0.9<\/h4>\n\n\n- Added asynchronous branch actions in the
All Managed Sets<\/code> overview so Fetch<\/code>, Pull<\/code>, and Push<\/code> no longer rely on a blocking full-page POST flow.<\/li>\n- Added modal-based operation progress UI, with indeterminate progress for fetch and determinate progress for push.<\/li>\n
- Added a first-commit guard so PushPull now requires
Fetch<\/code> before creating the first local commit when the remote branch already has history.<\/li>\n- Fixed push planning so unchanged remote objects are reused in the normal linear-history case instead of being counted and uploaded again.<\/li>\n<\/ol>\n\n
0.0.8<\/h4>\n\n\n- Added new managed content domains for WordPress custom CSS and WordPress pages.<\/li>\n
- Added a dedicated WordPress attachments domain with directory-backed repository storage using
attachment.json<\/code> plus the binary file.<\/li>\n- Added explicit opt-in attachment sync through a
Sync with PushPull<\/code> checkbox in the media library, so only marked attachments are managed.<\/li>\n- Added
wp_pattern_sync_status<\/code> to the owned WordPress block pattern meta allowlist.<\/li>\n- Refactored the sync engine so managed sets can supply authoritative repository files directly, allowing non-manifest adapter families like attachments.<\/li>\n<\/ol>\n\n
0.0.7<\/h4>\n\n\n- Fixed WordPress block pattern apply\/export escaping so
\\\\u002d<\/code> sequences survive correctly in both post_content<\/code> and pattern meta.<\/li>\n- Removed creation and modification timestamps from generic post-type canonical items to avoid false diffs across environments.<\/li>\n
- Changed the
All Managed Sets<\/code> overview so each managed set starts collapsed by default.<\/li>\n<\/ol>\n\n0.0.6<\/h4>\n\n\n- Fixed branch commits so committing one managed set no longer removes previously committed managed-set content from the same branch.<\/li>\n
- Reorganized the Managed Content admin UI so branch actions (
Pull<\/code>, Fetch<\/code>, Push<\/code>) appear only in the all-managed-sets overview, while per-managed-set views keep only managed-set actions.<\/li>\n- Moved remote branch reset into Settings alongside the local repository reset controls.<\/li>\n
- Added transparent current-site URL placeholder normalization for post-type-backed managed content so environment-local absolute URLs can round-trip across sites.<\/li>\n
- Split plugin runtime assets from WordPress.org listing assets, with packaging and SVN deploy updated to use the correct directories.<\/li>\n<\/ol>\n\n
0.0.5<\/h4>\n\n\n- Added GitHub-backed remote repository support using GitHub's Git Database API.<\/li>\n
- Added end-to-end commit, fetch, pull, merge, conflict resolution, apply, and push workflows in WordPress admin.<\/li>\n
- Added local and remote repository reset actions, audit logging, and operation locking.<\/li>\n
- Added support for multiple managed content domains, including GenerateBlocks conditions and WordPress block patterns.<\/li>\n
- Added release automation for packaging, Plugin Check, WordPress.org SVN deploy, and public GitHub sync.<\/li>\n<\/ol>\n\n
0.0.1<\/h4>\n\n
Initial public release focused on GitHub-backed synchronization of GenerateBlocks Global Styles.<\/p>","raw_excerpt":"Git-based content sync for WordPress.","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/tah.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/220400","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/tah.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin"}],"about":[{"href":"https:\/\/tah.wordpress.org\/plugins\/wp-json\/wp\/v2\/types\/plugin"}],"replies":[{"embeddable":true,"href":"https:\/\/tah.wordpress.org\/plugins\/wp-json\/wp\/v2\/comments?post=220400"}],"author":[{"embeddable":true,"href":"https:\/\/tah.wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/jeromesteunenberg"}],"wp:attachment":[{"href":"https:\/\/tah.wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=220400"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/tah.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=220400"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/tah.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=220400"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/tah.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=220400"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/tah.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=220400"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/tah.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=220400"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}