-
Notifications
You must be signed in to change notification settings - Fork 39
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Automate deployment of non functional assets to wp.org #827
Comments
@danieliser Just realized that we don't keep wp.org assets in the repo. Makes it difficult to hunt down the assets to switch them out and makes this automated deployment not possible. Should we add the wp.org assets to the repo and, if so, where? |
Yea that was part of #791 too, that is the only way to manage them via that action. |
@danieliser Looks like if we continue as planned to the 10up action above, they have a slug for us to point to which directory we use for the assets: I like their default |
@fpcorso Yea a |
…ess.org We are planning on eventually auto-deploying these so this is a good first step towards that. Issue #827
@danieliser Tested this on one of my tiny plugins. The 10up action will update the readme in So, we just need to add SVN credentials (see the thread in Slack). |
Utilizing GitHub actions or similar scripts, we can commit any readme and WordPress.org-specific assets changes to the WordPress.org plugin repository.
10up has an action for this already: https://github.com/10up/action-wordpress-plugin-asset-update
Originally apart of #711
The text was updated successfully, but these errors were encountered: