Setup WordPress.org Deployments via Tagged Releases Using GitHub Actions

[timnolte]

Drop using the a local/manual deployment process for releases and move to using tagging and a GitHub action to deploy releases to the WordPress.org repository.

Items to Address

• Deploying plugin build artifacts and not just files from the repository.
• Downloading translations from GlotPress.

[timnolte]

Gutenberg Build & Deployment Process

NOTE: There is a lot of code and process to manage with this setup but it allows for building an installable pluign release in GitHub and deploying a built version of the plugin to WP.org. The current 10up deployment action doesn't provide a solution for only uploading a built version of the plugin.

• Release Package Build: https://github.com/WordPress/gutenberg/blob/master/bin/build-plugin-zip.sh
• Release Package Action: https://github.com/WordPress/gutenberg/blob/master/.github/workflows/build-plugin-zip.yml
• WP.org Deployment Action: https://github.com/WordPress/gutenberg/blob/master/.github/workflows/upload-release-to-plugin-repo.yml

[timnolte]

New WordPress Deployment GitHub Action

A fork of the 10up GitHub Action was created that supports a build source directory. This version allows for the use of the existing Grunt build/release/deploy setup along with simply tagging the release. Some other items to consider for later is uploading a good release artifact to GitHub that is an installable version of the plugin.

• https://github.com/marketplace/actions/wordpress-plugin-svn-deploy