Automate release process with a GitHub action #471
Conversation
This file contains 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.
What?
Automate the release process of the plugin with a GitHub action.
Why?
To automate the process, lowering the effort of releasing new versions and avoiding the need to manually repeat tasks prone to errors.
How?
By adding a GitHub action.
There will be a new action in the 'actions' section of the repo. The user will be able to select the type of release to launch (patch, minor, major) and a PR will be created with the new version. If everything is OK with the newly created PR and it is merged to
masterbranch it will fire a release to the wordpress.org plugin directory.Demo
The code for this change was adapted from the Create Block Theme repo. Here is a screencast of the release process in that repo that this PR brings to Theme-check plugin.
Screencast.from.10-10-24.16.05.23.webm
Blocked by
The Github action assumes that the plugin is using semantic versioning.
The implementation of this action is blocked by: #469