PushPull stores selected WordPress content in a Git repository using a canonical JSON representation instead of raw database dumps.<\/p>\n\n
This project is also documented through a DevOps-focused article series that explains how to efficiently manage a WordPress stack with Bedrock and PushPull, starting here: https:\/\/creativemoods.pt\/devops-with-wordpress\/<\/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
Fetch<\/code> likely has updates available<\/li>\n- Bulk
Commit + Push All<\/code> and Pull + Apply All<\/code> workflows for whole-site bootstrap and deploy flows<\/li>\n- A
wp pushpull<\/code> WP-CLI command surface for status, configuration, domains, and sync operations<\/li>\n<\/ol>\n\nCurrent scope<\/h3>\n\n
This is an early, focused release. At the moment, PushPull is intentionally limited to:<\/p>\n\n
\n- GitHub and GitLab as implemented remote providers<\/li>\n
- Managed domains across three families:\n generateblocks\/global-styles\/\n generateblocks\/conditions\/\n wordpress\/block-patterns\/\n wordpress\/categories\/\n wordpress\/comments\/\n wordpress\/menus\/\n wordpress\/pages\/\n wordpress\/posts\/\n wordpress\/tags\/\n wordpress\/custom-css\/\n wordpress\/attachments\/\n wordpress\/configuration\/\n wpml\/configuration\/\n wordpress\/generatepress-elements\/\n wordpress\/custom-post-types\/\/\n wordpress\/custom-taxonomies\/\/\n translations\/management\/\n media\/organization\/<\/li>\n
- Canonical JSON storage with one file per managed item for manifest-backed sets, plus directory-backed storage for attachments using
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
- A cached remote-head availability signal for
Fetch<\/code>, driven by a configurable recurring check instead of a live provider probe on every page load<\/li>\n<\/ol>\n\nIt does not yet manage forms, users, 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
- Optionally set the remote fetch check interval in minutes<\/li>\n
- Click
Test connection<\/code><\/li>\n- Save the settings<\/li>\n<\/ol>\n\n
Domain selection<\/h4>\n\n
In PushPull > Domains:<\/p>\n\n
\n- Enable one or more managed domains<\/li>\n
- Review WordPress core, installed plugin integrations, and discovered custom content separately<\/li>\n
- Opt into generic discovered custom post types and taxonomies when you want them managed<\/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\nPushPull also performs a lightweight recurring remote-head check and visually highlights Fetch<\/code> when the latest scheduled check suggests the remote branch has advanced since the last fetch.<\/p>\n\nFor whole-site bootstrap flows, PushPull also supports:<\/p>\n\n
\nCommit + Push All<\/code> to snapshot and publish all enabled domains<\/li>\nPull + Apply All<\/code> to import and apply all enabled domains on a bare target site<\/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
WP-CLI<\/h4>\n\n
PushPull also exposes a wp pushpull<\/code> command.<\/p>\n\nExamples:<\/p>\n\n
\nwp pushpull status<\/code><\/li>\nwp pushpull domains<\/code><\/li>\nwp pushpull config list<\/code><\/li>\nwp pushpull config set branch main<\/code><\/li>\nwp pushpull config enable-domain wordpress_pages<\/code><\/li>\nwp pushpull commit wordpress_pages<\/code><\/li>\nwp pushpull push<\/code><\/li>\nwp pushpull commit-push-all<\/code><\/li>\nwp pushpull pull-apply-all<\/code><\/li>\n<\/ol>\n\nEmpty 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 Categories, WordPress Comments, WordPress Menus, WordPress Pages, WordPress Posts, WordPress Tags, WordPress Custom CSS, GeneratePress Elements, explicitly opted-in WordPress Attachments, WordPress core configuration, WPML configuration, generic discovered custom post types and taxonomies, 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
Install via Composer \/ Packagist<\/h4>\n\n
In a Composer-managed WordPress project such as Bedrock:<\/p>\n\n
\n- Require the plugin:\n composer require creativemoods\/pushpull<\/li>\n
- Make sure the root project allows
composer\/installers<\/code> and installs type: wordpress-plugin<\/code> packages into your plugins directory<\/li>\n- Activate PushPull in WordPress.<\/li>\n<\/ol>\n\n\n
See the full release history in CHANGELOG.md<\/code>.<\/p>","raw_excerpt":"Git-based content sync for WordPress. Project homepage: https:\/\/creativemoods.pt\/pushpull\/","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/ga.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/220400","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/ga.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin"}],"about":[{"href":"https:\/\/ga.wordpress.org\/plugins\/wp-json\/wp\/v2\/types\/plugin"}],"replies":[{"embeddable":true,"href":"https:\/\/ga.wordpress.org\/plugins\/wp-json\/wp\/v2\/comments?post=220400"}],"author":[{"embeddable":true,"href":"https:\/\/ga.wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/jeromesteunenberg"}],"wp:attachment":[{"href":"https:\/\/ga.wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=220400"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/ga.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=220400"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/ga.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=220400"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/ga.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=220400"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/ga.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=220400"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/ga.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=220400"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}