Enable wp.org deploy and add directory screenshots#99
Merged
Conversation
Uncomments the wporg-deploy job in the publish workflow now that the plugin has been approved for the WordPress.org plugin directory. Moves BUILD_DIR/ASSETS_DIR/SLUG under env: since the 10up action reads them from the environment, not from with: inputs. Adds four 1280x900 screenshots (Compose panel, toolbar AI actions, notes sidebar, pre-publish checks) and updates readme.txt to match.
✅ Coverage Report — plugin-php
✅ Coverage Report — plugin-typescript
✅ Coverage Report — typescript
|
There was a problem hiding this comment.
Pull request overview
Enables automated deployment of the WordPress plugin to the WordPress.org directory and updates the plugin’s directory-facing assets/documentation to match the new screenshots.
Changes:
- Re-enables the
wporg-deployGitHub Actions job to deploy the plugin to WordPress.org via 10up’s deploy action. - Updates
readme.txtscreenshot descriptions to match the new set/order of screenshots. - Adds new WordPress.org directory screenshots under
wordpress-plugin/.wordpress-org/(per PR description) for upload on tag pushes.
Reviewed changes
Copilot reviewed 2 out of 6 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
.github/workflows/publish.yml |
Re-enables the WordPress.org deploy job and sets required deploy configuration via environment variables. |
wordpress-plugin/readme.txt |
Updates the Screenshots section entries to align with the new directory screenshots. |
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.
Summary
wporg-deployjob in.github/workflows/publish.ymlnow that the plugin is approved for the WordPress.org directory.BUILD_DIR/ASSETS_DIR/SLUGmoved underenv:— the 10up action reads them as environment variables, not aswith:inputs (verified from itsaction.yml;SVN_USERNAMEandSVN_PASSWORDrepo secrets are already configured).wordpress-plugin/.wordpress-org/, which the 10up action uploads to SVNassets/on the next tag push: Compose panel mid-outline, block toolbar AI actions dropdown, notes sidebar with per-note actions, pre-publish checks with AI suggestions.== Screenshots ==entries inwordpress-plugin/readme.txtto match the four images in order.Test plan
v0.4.2) after bumpingwordpress-plugin/claudaborative-editing.phpandreadme.txt'sStable tag:, and watch thewporg-deployjob complete.https://wordpress.org/plugins/claudaborative-editing/shows the four screenshots in the listed order post-deploy.sips -g pixelHeight wordpress-plugin/.wordpress-org/screenshot-*.png(all should be 900).