chore: remove the Playground preview workflows - #38
Open
josephfusco wants to merge 1 commit into
Open
Conversation
josephfusco
marked this pull request as ready for review
August 20, 2026 22:13
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #38 +/- ##
=========================================
Coverage 63.90% 63.90%
Complexity 35 35
=========================================
Files 7 7
Lines 266 266
=========================================
Hits 170 170
Misses 96 96
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
These three workflows have never worked. Playground Preview Publish has failed on all 8 of its runs, and the causes date to 52c0077, the commit that introduced them -- there was never a working version to regress from. Because publish runs on `workflow_run`, its failures never appeared in `gh pr checks` and never gated a PR, so it sat broken unnoticed for the repo's entire history. The breakage is structural rather than a small fix: - `test -f artifacts/release-assets/` tests a directory, which is always false under `bash -e`; this kills the job ~10s in, before anything else runs. - Two of the three release assets (a "seeder" and a "helper") were scaffolded as bare paths with the filenames never filled in, and no such files exist anywhere in the repo. The build stages only sync-storage.zip. - blueprint-40.json, transformed on line 141 and advertised in the sticky comment as a "40 demo users" variant, was never created. - blueprint.json has no writeFile steps, so the seeder/helper half of the jq transform is a no-op regardless, and its two `endswith("/")` branches are identical, leaving the elif unreachable. Nothing depends on them: no Playground job is a required status check, nothing outside the three files references them, and no preview-pr-* releases or tags were ever produced. Deleting is honest about the state of things; if per-PR previews are wanted later, they are better rebuilt than repaired. blueprint.json stays -- the README badge points Playground at it directly via raw.githubusercontent.com and never involved these workflows.
josephfusco
force-pushed
the
chore/remove-playground-previews
branch
from
August 20, 2026 22:18
566a1e6 to
991c664
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Deletes
playground-preview.yml,playground-preview-publish.yml, andplayground-preview-cleanup.yml.Why
Playground Preview Publish has failed on all 8 of its runs, three of them today. Because it runs on
workflow_run, its failures never show ingh pr checksand never gate a PR — so it sat broken unnoticed.I traced the causes to
52c0077, the commit that first added these workflows. There was never a working version to regress from; they went in broken.The breakage is structural, not a typo:
test -f artifacts/release-assets/tests a directory, always false underbash -e. Kills the job ~10s in, before anything else runs.artifacts/release-assets/) with filenames never filled in — and no such files exist in the repo.playground-preview.yml:69stages onlysync-storage.zip.blueprint-40.jsondoesn't exist. It's transformed on line 141 and advertised in the sticky comment as a "40 demo users" variant.blueprint.jsonhas nowriteFilesteps, so the seeder/helper half of the jq transform is a no-op regardless. Its twoendswith("/")branches (132–133) are byte-identical, making theelifunreachable.The sticky comment also advertised "seeds 5 demo users," which
blueprint.jsonnever did — it creates thewp_collaborationtable and activates plugins.Safety
gate,phpcs,phpstan,phpunit×2,typos,plugin-check)preview-pr-*releases or tags were ever produced — consistent with publish never succeedingactionlintclean on the remaining workflowsblueprint.jsonis kept. The README badge points Playground at it directly viaraw.githubusercontent.comand never involved these workflows.If per-PR previews are wanted later, they're better rebuilt than repaired.
Use of AI Tools
Assisting with the audit and removal.