Install
Upload it under Plugins → Add New Plugin → Upload Plugin, then activate.
Install straight from GitHub with WP-CLI:
wp plugin install https://github.com/jesgs-interactive/wp-block-forker/releases/download/v0.2.0/wp-block-forker.zipSelect blocks in the WordPress block editor and fork them into a new post — as a copy or a move.
Requirements
- WordPress 6.5+
- PHP 8.1+
- Node 20+ (only for building from source — not required to run an already-built release zip)
- Composer (only for building a local distribution zip — see below; not required to build from source for local dev, and not required to run an already-built release zip)
Install
Download wp-block-forker.zip from the latest GitHub release and install it
normally via Plugins → Add New → Upload Plugin. The plugin checks
GitHub Releases for updates automatically once installed (see
AGENTS.md → Release process).
Building from source
npm ci
npm run build
This compiles src/ into build/, which the PHP side requires at runtime.
build/ is gitignored — always run the build before activating a plugin
checked out from source.
To build a distributable zip locally (what a GitHub release would produce, without tagging one):
composer install
vendor/bin/phing dist
Produces build-dist/wp-block-forker.zip. See AGENTS.md for what it
excludes and how it relates to the release workflow.
Usage
Select one or more blocks → block toolbar "⋮" menu → "Fork to new post…" → set a title, pick a post type if more than one is available, choose copy or move → Fork.
See AGENTS.md for architecture, the REST API contract, and design
decisions worth knowing before changing anything.
Releases
1 release. Each count is every asset in that release; expand a row for the breakdown.