Playground PR review support for two-factor

[masteradhoc]

What?

Add a WordPress Playground preview button to pull requests.

Fixes #774

Why?

Makes it easier to test plugin changes without a local environment — reviewers can click a button directly from the PR to try the changes in a live Playground instance.

How?

Two new workflows:

• build-plugin-zip.yml — builds the plugin and uploads it as an artifact on every PR
• pr-playground-preview.yml — triggers after the build, exposes the artifact publicly, and appends a Playground preview button to the PR description

Testing Instructions

1. Open a pull request
2. Wait for both Build Plugin Zip workflow to complete
3. download the zip created over the workflow over Actions tab in github repo
4. extract it and install the "two-factor" zip inside
5. test the changes made in this PR

Whats not testable yet: PR Playground Preview.
The reason is a GitHub limitation with workflow_run — workflows using that trigger must exist on the default branch to work. Since pr-playground-preview.yml only exists on this feature branch (not yet merged to master), GitHub ignores it.

Changelog Entry

Added - Playground preview button on pull requests for easier testing.

[github-actions]

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

Core SVN

If you're a Core Committer, use this list when committing to wordpress-develop in SVN:

Props: masteradhoc, georgestephanis, jeffpaul.

GitHub Merge commits

If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.

Co-authored-by: masteradhoc <masteradhoc@git.wordpress.org>
Co-authored-by: georgestephanis <georgestephanis@git.wordpress.org>
Co-authored-by: jeffpaul <jeffpaul@git.wordpress.org>

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

[georgestephanis]

It feels like we can skip the build plugin zip workflow, and instead rely on the new git:directory

https://make.wordpress.org/playground/2025/12/19/action-required-github-proxy-com-shutdown/

https://wordpress.github.io/wordpress-playground/blueprints/steps/resources/#gitdirectoryreference

hat tip to @fellyph for posting about the update!

[kasparsd]

Noting that we have this Grunt task for generating the Blueprint URL:

two-factor/Gruntfile.js

Lines 50 to 56 in ab51db1

	grunt.registerTask(
	'blueprint-url',
	function() {
	const blueprintJson = JSON.parse( fs.readFileSync( '.wordpress-org/blueprints/blueprint.json', 'utf8' ) );
	grunt.log.write( `Blueprint URL: https://playground.wordpress.net/#${ encodeURI( JSON.stringify( blueprintJson ) ) }` );
	}
	);

It appears that Blueprints support GitHub origin:

https://github.com/WordPress/blueprints/blob/920a455150e16f411b56ccf59e86966c194f2758/apps/ai-assistant.json#L15-L20

so we can skip the ZIP generation completely and let it pull the specific branch name. So maybe have a Grunt task that pulls the default blueprint.json and updates the installPlugin step to use the branch origin of the current pull request?