Conversation
Add deploy.yml (release-triggered SVN deploy with npm build step) and asset-deploy.yml (push-to-main asset/readme update). Adapted from the progress-planner workflows; deploy.yml additionally runs npm ci and npm run build so the gitignored build/ directory is generated before the 10up action ships to wp.org. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> Signed-off-by: Filip Ilic <ilic.filip@gmail.com>
Add workflow_dispatch to both deploy.yml and asset-deploy.yml so the SVN push and asset/readme update can be run on demand from the Actions tab. Useful for the initial 1.0.0 ship since the GitHub release was created before the workflows existed, and as an escape hatch for re-running a failed deploy. Skip the GitHub release asset upload step on manual runs, since github.event.release isn't populated then. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> Signed-off-by: Filip Ilic <ilic.filip@gmail.com>
Add WordPress.org SVN deploy workflows
Contributor
|
Test on Playground |
ilicfilip
changed the title
Contributor
✅ WordPress Plugin Check Report
📊 ReportAll checks passed! No errors or warnings found. 🤖 Generated by WordPress Plugin Check Action • Learn more about Plugin Check |
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
1 participant
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.
Summary
Release merge:
develop→mainfor the initial 1.0.0 wp.org ship.Brings in:
deploy.yml(release-triggered, manual-dispatchable) andasset-deploy.yml(push-to-main, manual-dispatchable).Release flow
Once this merges:
asset-deploy.ymlfires automatically on the push tomainand syncs.wordpress-org/+readme.txtto wp.org.deploy.ymlmanually from the Actions tab (branchmain) to build and push the plugin code to SVN trunk +tags/1.0.0. The existing 1.0.0 GitHub release predates the workflow, so manual dispatch is used instead of recreating the release.🤖 Generated with Claude Code