Skip to content

Chore/blueprint#13

Merged
firestar300 merged 4 commits intodevelopfrom
chore/blueprint
Mar 26, 2026
Merged

Chore/blueprint#13
firestar300 merged 4 commits intodevelopfrom
chore/blueprint

Conversation

@firestar300
Copy link
Copy Markdown
Collaborator

@firestar300 firestar300 commented Mar 26, 2026

Note

Low Risk
Documentation and developer-experience changes only; no plugin runtime code or data/security-sensitive logic is modified.

Overview
Adds a WordPress Playground entrypoint by introducing blueprint.json, which logs in and installs/activates the plugin from the 1.0.4 tag.

Updates README.md to include a “Test with WordPress Playground” badge linking to that blueprint for one-click demos/testing.

Written by Cursor Bugbot for commit f2ff849. This will update automatically on new commits. Configure here.

Adds a blueprint.json configuration to allow users to test the plugin in a WordPress Playground environment and includes a "Test with WordPress Playground" badge in the README.
@firestar300 firestar300 merged commit 5627223 into develop Mar 26, 2026
2 of 4 checks passed
Copy link
Copy Markdown

@cursor cursor bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cursor Bugbot has reviewed your changes and found 1 potential issue.

Fix All in Cursor

Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.

"resource": "git:directory",
"url": "https://github.com/BeAPI/blockparty-modal",
"ref": "1.0.4",
"refType": "tag"
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hardcoded version tag will become stale

Low Severity

The ref in blueprint.json is hardcoded to "1.0.4" with refType: "tag", while the README badge always reads this file from the main branch. This means future releases will still demo version 1.0.4 in WordPress Playground unless this file is manually updated each time. Using "ref": "main" with "refType": "branch" would keep the demo in sync automatically without a manual update step on every release.

Fix in Cursor Fix in Web

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant