Automate deployment of non functional assets to wp.org

[fpcorso]

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

[fpcorso]

@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?

[danieliser]

Yea that was part of #791 too, that is the only way to manage them via that action.

[fpcorso]

@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 .wordpress-org folder which would sit alongside our .github folder as another non-development directory. Are you good with keeping that directory name?

[danieliser]

@fpcorso Yea a . folder keeps it well out of the normal structures.

[fpcorso]

@danieliser Tested this on one of my tiny plugins. The 10up action will update the readme in trunk and in the tag folder that matches the stable tag. It did not touch any other files so it should be good.

So, we just need to add SVN credentials (see the thread in Slack).