Skip to content

feat: add playground support #1659

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: develop
Choose a base branch
from
Open

feat: add playground support #1659

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 14 additions & 0 deletions .wordpress-org/blueprints/blueprint.json
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,14 @@
{
"landingPage": "/wp-admin/",
"preferredVersions": {
"php": "8.0",
"wp": "latest"
},
"plugins": ["wp-user-frontend"],
"steps": [
{
"step": "login",
"username": "admin"
}
]
}
Comment on lines +1 to +14
Copy link

@coderabbitai coderabbitai bot Jul 30, 2025

Choose a reason for hiding this comment

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

💡 Verification agent

🧩 Analysis chain

CI can’t find / parse the blueprint – verify path & expected format

The pipeline reports
ERROR: The file ".wordpress-org/blueprints/blueprint.json" does not exist and an XML-related parse error (Start tag expected, '<' not found).
This usually happens when:

  1. The consumer is looking for .wordpress-org/blueprint.json (no blueprints/ sub-dir) or a different extension, or
  2. The CI task expects an XML blueprint, not JSON.

Until the file is in the exact location/format the job expects, “playground support” will remain broken.

Please double-check the spec used by the WordPress Playground action (or whatever step consumes this file) and rename / relocate / convert accordingly.

🏁 Script executed:

#!/bin/bash
set -e

echo "=== Listing all blueprint.json files ==="
fd blueprint.json || echo "No blueprint.json files found."

echo
echo "=== Searching for 'blueprint' references in GitHub Actions workflows ==="
rg -n "blueprint" .github/workflows || echo "No references to 'blueprint' in workflows."

echo
echo "=== Searching for 'blueprints/' directory references ==="
rg -n "blueprints/" -C2 .

Length of output: 630

CI Blueprint Path Mismatch
The CI job is currently unable to locate your blueprint because it’s expecting a different path or format. The file lives at:
• .wordpress-org/blueprints/blueprint.json
but the pipeline error indicates it’s looking for:
• .wordpress-org/blueprint.json
(or an XML-formatted blueprint).

Please verify the WordPress Playground action’s spec and update one of the following so they match:

• Move or rename the file to .wordpress-org/blueprint.json
• Update your workflow/config to point at blueprints/blueprint.json
• If the action requires XML rather than JSON, convert the blueprint to the expected format

Once the path and format align, “playground support” will be restored.

🧰 Tools
🪛 GitHub Actions: Inspections

[error] 1-1: Error: Start tag expected, '<' not found on line 1, column 1. The file may be malformed or not an XML file.

[error] 1-1: ERROR: The file ".wordpress-org/blueprints/blueprint.json" does not exist.

🤖 Prompt for AI Agents 
In .wordpress-org/blueprints/blueprint.json lines 1 to 14, the CI pipeline
cannot find the blueprint because it expects the file at
.wordpress-org/blueprint.json or in XML format. To fix this, either move or
rename the current JSON file to .wordpress-org/blueprint.json, or update the CI
workflow configuration to point to blueprints/blueprint.json. If the action
requires XML format, convert the JSON blueprint to XML accordingly.

18 changes: 18 additions & 0 deletions .github/workflows/asset-deploy.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,18 @@
name: Plugin asset/readme update
on:
push:
branches:
- master
jobs:
trunk:
name: Push to trunk
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@master
Copy link

@coderabbitai coderabbitai bot Jul 30, 2025

Choose a reason for hiding this comment

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

🛠️ Refactor suggestion

Use a maintained version of actions/checkout

actions/checkout@master is deprecated. Switch to the latest tagged release (currently v4) or pin to a specific commit for supply-chain safety.

-    - uses: actions/checkout@master
+    - uses: actions/checkout@v4
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
- uses: actions/checkout@master
- uses: actions/checkout@v4
🤖 Prompt for AI Agents 
In .github/workflows/asset-deploy.yml at line 11, replace the deprecated
'actions/checkout@master' with the latest stable tagged release, such as
'actions/checkout@v4', to ensure the action is maintained and improve
supply-chain security.

- name: WordPress.org plugin asset/readme update
uses: 10up/action-wordpress-plugin-asset-update@stable
env:
SVN_PASSWORD: ${{ secrets.SVN_PASSWORD }}
SVN_USERNAME: ${{ secrets.SVN_USERNAME }}
SLUG: wp-user-frontend
Comment on lines +13 to +17
Copy link

@coderabbitai coderabbitai bot Jul 30, 2025

Choose a reason for hiding this comment

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

🛠️ Refactor suggestion

Pin external action to a commit or tag

10up/action-wordpress-plugin-asset-update@stable floats with every push to the stable branch.
For reproducible builds and better supply-chain security, pin to a full SHA or semver tag:

-    - name: WordPress.org plugin asset/readme update
-      uses: 10up/action-wordpress-plugin-asset-update@stable
+    - name: WordPress.org plugin asset/readme update
+      uses: 10up/action-wordpress-plugin-asset-update@v2.2.1 # <-- example; replace with latest tag/SHA
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
uses: 10up/action-wordpress-plugin-asset-update@stable
env:
SVN_PASSWORD: ${{ secrets.SVN_PASSWORD }}
SVN_USERNAME: ${{ secrets.SVN_USERNAME }}
SLUG: wp-user-frontend
- name: WordPress.org plugin asset/readme update
uses: 10up/action-wordpress-plugin-asset-update@v2.2.1 # <-- example; replace with latest tag or full SHA
env:
SVN_PASSWORD: ${{ secrets.SVN_PASSWORD }}
SVN_USERNAME: ${{ secrets.SVN_USERNAME }}
SLUG: wp-user-frontend
🤖 Prompt for AI Agents 
In .github/workflows/asset-deploy.yml around lines 13 to 17, the GitHub action
uses a floating tag 'stable' for 10up/action-wordpress-plugin-asset-update,
which can change unexpectedly. To fix this, replace 'stable' with a specific
commit SHA or a fixed semver tag to ensure reproducible builds and improve
supply-chain security.

IGNORE_OTHER_FILES: true
Loading