Simplify GitHub Actions and document testing and releases - #73
Merged
Merged
Conversation
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
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.
Summary
Consolidate the overlapping Actions entry points into four named workflows: Code standards, Plugin tests, Live Siteimprove test, and Create and deploy release, plus the shared release-check helper.
mainandwp-*deployment triggers. Dry runs create no GitHub release and perform no SVN operations. Test mode requires a separate SVN destination. Serialize release runs.docs/workflows.md, link it from README, and replace obsolete deployment instructions with the current procedures, report locations and live-test limitations.Validation
Release behavior
Plain
vMAJOR.MINOR.PATCHtag pushes still validate and publish automatically.-dry-runand-testsuffixes select their respective modes; manual runs select an existing version tag and default to dry-run. All modes retain the shared validation, including the protected live check. The live missing-title result assertion remains skipped and is documented explicitly.