Repository navigation
Replace asset update with WordPress.org plugin page workflow - #69
Draft
InpsydeNiklas wants to merge 1 commit into
Draft
InpsydeNiklas wants to merge 1 commit into
InpsydeNiklas wants to merge 1 commit into
Conversation
🔍 WordPress Plugin Check Report
📊 Report
|
| 📍 Line | 🔖 Check | 💬 Message |
|---|---|---|
169 |
WordPress.NamingConventions.PrefixAllGlobals.DynamicHooknameFound | Hook names invoked by a theme/plugin should start with the theme/plugin prefix. Found: "self::FILTER_MAX_SITES". |
🤖 Generated by WordPress Plugin Check Action • Learn more about Plugin Check
lloc
force-pushed
the
ci/wordpress-org-plugin-page
branch
from
October 26, 2026 12:26
6c9745b to
b1d963c
Compare
lloc
force-pushed
the
ci/wordpress-org-plugin-page
branch
from
October 26, 2026 12:30
b1d963c to
47cb6c8
Compare
The old assets-update workflow pushed readme.txt and .wordpress-org/ to WordPress.org on every push to main. With main becoming the built branch, that trigger no longer fits, and publishing should be a deliberate step anyway. The new workflow calls the inpsyde wordpress-org-plugin-page reusable workflow and only runs when dispatched manually. A dry run is the default, so a run only previews the SVN changes and the readme diff until DRY_RUN is turned off. The assets are validated (names, dimensions, sizes, blueprints) before anything is synced, and .wordpress-org/ is mirrored to SVN /assets. The readme is synced to the Stable tag and trunk only when SYNC_README is on. GIT_REF is the dispatched commit, never free text. The reusable workflow is pinned to the head of inpsyde/reusable-workflows#296 until that PR is merged.
lloc
force-pushed
the
ci/wordpress-org-plugin-page
branch
from
October 27, 2026 11:12
47cb6c8 to
0b8d277
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.
This replaces
assets-update.yml(the 10up asset update on every push tomain) with a manual WordPress.org plugin page workflow, built onwordpress-org-plugin-page.ymlfrominpsyde/reusable-workflows.Stacked on #68 (release), which is stacked on #67. Review only the last commit until both are merged.
Behavior change: nothing is published automatically any more. Readme and asset changes reach WordPress.org only when someone runs the workflow from
dev/main, and the readme is synced only whenSYNC_READMEis on.What changes
Manual only, from
dev/mainonly. The workflow isworkflow_dispatchonly, and the job is skipped on any other ref, so a feature branch can't reach the plugin page.Inputs:
SYNC_README,SYNC_ASSETSandDRY_RUN, all defaulttrue. A dry run is the default. It shows the SVN status and the readme diff against theStable tag, and uploads exactly what would be committed.Asset validation before syncing:
blueprints/*.jsonThen
.wordpress-org/is mirrored to SVN/assets, so files removed from Git are removed from WordPress.org too.GIT_REFis the dispatched commit (github.sha), never free text. The token is read-only.The concurrency group
wordpress-org-svnis shared with releases.CONTRIBUTING.mddocuments the flow: merge todev/main, dry run, review, then run withDRY_RUNoff.Release Confirmation is not enabled for
multisyde, so syncing the readme into the stable tag is supported.Tested
On a local Gitea, against the real WordPress.org SVN with dummy credentials:
DRY_RUN=falsefails at the SVN commit with an authentication errorOnly verifiable here on GitHub: the boolean inputs reaching the called workflow. A Gitea bug passes them through
workflow_callasfalse, so locally the logic was tested by running a copy of the reusable workflow directly.Draft until inpsyde/reusable-workflows#296 is merged. The reusable workflow is pinned to that PR's head (
5f66316) for now and gets re-pinned to its merge commit before this is marked ready.