Add GitHub Actions workflow for WordPress.org plugin updates#45
Merged
Conversation
…ns at the top level
dkotter
approved these changes
Apr 14, 2026
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
2 participants
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.
Description of the Change
Copilot summary
This pull request introduces a new GitHub Actions workflow to automate updating plugin assets and the readme file on WordPress.org whenever changes are pushed to the
mainbranch.CI/CD automation:
.github/workflows/wporg-plugin-asset-update.ymlthat checks out the code, sets up Node.js, installs dependencies, builds the project, and uses the 10up WordPress plugin asset update action to push changes to the WordPress.org plugin repository.How to test the Change
Changelog Entry
Credits
Props @jeffpaul.
Checklist: