WP Branches For Post provides a Git-like editorial workflow for WordPress content.<\/p>\n\n
Instead of editing a published post in place, create a draft branch. The public original remains unchanged while the branch is edited. When the work is ready, explicitly merge the branch back into the same original post ID.<\/p>\n\n
Version 2.0 modernizes the original 2020 plugin for the current WordPress block editor and REST API.<\/p>\n\n
During merge, the plugin synchronizes editable post content, post meta, and all taxonomies while preserving the original post identity and publication state.<\/p>\n\n
Media IDs referenced by post content and featured-image meta remain the same. Attachments are not re-parented.<\/p>\n\n
The Post Branch document panel shows:<\/p>\n\n
Classic Editor, post-list row actions, and the admin bar retain lightweight compatibility controls.<\/p>\n\n
Version 2.0 recognizes branches created by the 1.x metadata format.<\/p>\n\n
Legacy branches do not contain a baseline snapshot, so they are reported as \"unknown\" conflict state and require an explicit force merge after the original has been reviewed.<\/p>\n\n
The old automatic \"publish branch to overwrite original\" behavior has intentionally been removed.<\/p>\n\n
WP Branches For Post is maintained by Hao Kexin, a full-stack engineer and product builder based in Japan. Since 2018, his work has spanned requirements, system design, application development, data systems, deployment, observability, and long-term production operations.<\/p>\n\n
His current work focuses on public data, financial analysis, AI, and end-to-end product engineering. He builds and maintains projects including Time2Analyze, a production system for public-company disclosures, structured financial data, analysis, Excel, MCP, and AI workflows.<\/p>\n\n
More about the author and current projects: https:\/\/time2log.com\/about\/<\/p>\n\n
Useful filters and actions include:<\/p>\n\n
wbfp_branchable_post_statuses<\/code><\/li>\nwbfp_create_branch_post_data<\/code><\/li>\nwbfp_excluded_meta_keys<\/code><\/li>\nwbfp_mergeable_post_fields<\/code><\/li>\nwbfp_branch_created<\/code><\/li>\nwbfp_before_merge<\/code><\/li>\nwbfp_after_merge<\/code><\/li>\n<\/ul>\n\nSecurity-critical invariants remain enforced after extension filters run: a new branch stays a draft of the same post type, required runtime meta stays excluded, and mergeable core fields are limited to the plugin's editorial allowlist.<\/p>\n\n
See ARCHITECTURE.md<\/code> for the create\/merge data flow and SECURITY.md<\/code> for authorization, CSRF, REST, conflict, and data-synchronization boundaries.<\/p>\n\nCI is intentionally not triggered for every feature-branch commit. Full PHP\/build\/Plugin Check validation runs on master<\/code>, release tags, or manual workflow dispatch.<\/p>\n\nThe Block Editor source is in src\/index.js<\/code> and is built with @wordpress\/scripts<\/code>.<\/p>\n\nHuman-readable source code and build tooling are maintained at https:\/\/github.com\/hsxk\/WP-Branches-For-Post\/.<\/p>\n\n\n
\n- Upload the plugin to
\/wp-content\/plugins\/wp-branches-for-post<\/code>, or install it through the WordPress Plugins screen.<\/li>\n- Activate WP Branches For Post.<\/li>\n
- Open an existing published post and use the Post Branch panel or Create Branch action.<\/li>\n<\/ol>\n\n\n
\nDoes a branch get a public URL?<\/h3><\/dt>\nNo. A branch is an isolated working draft. Publishing a branch through the normal editor is prevented; use Merge into original instead.<\/p><\/dd>\n
Does merging change the original URL or post ID?<\/h3><\/dt>\nNo. The merge updates the existing original post record and preserves its identity, slug, publication state, author, and original dates.<\/p><\/dd>\n
What happens if someone edits the original while I am working on a branch?<\/h3><\/dt>\nThe stored baseline snapshot no longer matches. The plugin marks the branch as conflicted and blocks the normal merge so newer work is not silently overwritten.<\/p><\/dd>\n
Can I still merge an old 1.x branch?<\/h3><\/dt>\nYes, but because 1.x did not store a baseline snapshot, the plugin requires an explicit force merge after review.<\/p><\/dd>\n
Does it support custom post types?<\/h3><\/dt>\nYes, when the user can edit the post and the post type uses the normal WordPress editing APIs. Taxonomies and post meta are synchronized with the branch.<\/p><\/dd>\n\n<\/dl>\n\n\n
2.0.0<\/h4>\n\n\n- Rebuilt the branch workflow for modern WordPress.<\/li>\n
- Added Block Editor document sidebar integration.<\/li>\n
- Added REST endpoints with capability-based permission callbacks.<\/li>\n
- Added baseline snapshot conflict detection.<\/li>\n
- Replaced publish-triggered merge with explicit merge actions.<\/li>\n
- Prevented branch posts from becoming public.<\/li>\n
- Reworked post meta synchronization to preserve multi-value keys and removals.<\/li>\n
- Reworked taxonomy synchronization so cleared taxonomies are also propagated.<\/li>\n
- Removed direct SQL revision and attachment-parent manipulation.<\/li>\n
- Preserve original post ID, URL, status, author, slug, and publication dates during merge.<\/li>\n
- Move merged\/discarded branches to Trash instead of permanently deleting them.<\/li>\n
- Added compatibility handling for branches created by version 1.x.<\/li>\n
- Added modern development tooling and CI syntax\/build checks.<\/li>\n<\/ul>\n\n
1.3.0<\/h4>\n\n\n- Added developer filters and code cleanup.<\/li>\n<\/ul>\n\n
1.2.0<\/h4>\n\n\n- Added zh_CN, zh_TW, and ja translations.<\/li>\n<\/ul>\n\n
1.1.0<\/h4>\n\n\n- Added admin-bar\/list actions and initial block-editor support.<\/li>\n<\/ul>\n\n
1.0.0<\/h4>\n\n\n- Initial release.<\/li>\n<\/ul>","raw_excerpt":"Create an isolated working branch for a published post, edit it safely, then explicitly merge it back into the original post.","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/es-do.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/118090","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/es-do.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin"}],"about":[{"href":"https:\/\/es-do.wordpress.org\/plugins\/wp-json\/wp\/v2\/types\/plugin"}],"replies":[{"embeddable":true,"href":"https:\/\/es-do.wordpress.org\/plugins\/wp-json\/wp\/v2\/comments?post=118090"}],"author":[{"embeddable":true,"href":"https:\/\/es-do.wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/haokexin"}],"wp:attachment":[{"href":"https:\/\/es-do.wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=118090"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/es-do.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=118090"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/es-do.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=118090"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/es-do.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=118090"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/es-do.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=118090"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/es-do.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=118090"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}