Skip to content

Add PR build ZIP workflow - #105

Closed
tg-autopilot wants to merge 4 commits into
masterfrom
tg-autopilot/add-pr-build-zip
Closed

tg-autopilot wants to merge 4 commits into
masterfrom
tg-autopilot/add-pr-build-zip

Conversation

@tg-autopilot

Copy link
Copy Markdown
Contributor

Adds a caller workflow for the reusable pr-build-zip.yml in wpeverest/.github.

On every PR (opened/synced/reopened/ready-for-review) this builds an installable plugin/theme ZIP and posts a download link as a PR comment, so a real ZIP is one click away from the code diff.

The build-command, package-manager, and zip-glob below were auto-detected from this repo's package.json/Gruntfile.js/gulpfile.js by an automated rollout script, not hand-written for this repo specifically. The first real PR opened against this branch is the actual test of whether the detected command produces a working ZIP in the expected place -- please double-check the with: block matches how this repo is actually packaged for release before relying on it, and adjust if the build fails.

lihsaa591 added a commit that referenced this pull request Sep 22, 2026
Supersedes the stalled PR #105, which used yarn (this repo has never
used yarn -- no yarn.lock exists, npm/package-lock.json is what's
actually used) and predates this branch's PHPCS/composer.json setup.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
@lihsaa591

Copy link
Copy Markdown
Contributor

Superseded by #109, which adds the corrected version of this workflow (package-manager: npm, not yarn -- this repo has never used yarn, no yarn.lock exists here, so this PR's build-command: yarn run build would never have worked regardless of secrets).

@lihsaa591 lihsaa591 closed this Sep 22, 2026
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.

2 participants