refactor: reusable WP.org release workflow #226
Merged
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.
The repos migrating from CircleCI to GitHub Actions that publish to WP.org had a
release-wporgjob that did a fresh checkout +npm cibut never built therelease/directory thatrelease-wporg.shexpects.In CircleCI, this worked via
persist_to_workspace/attach_workspace. This PR tries to bridge that gap usingupload-artifact/download-artifact:reusable-release-wporg.yml, a reusable workflow for publishing to WordPress.org that downloads release artifacts from the release job and runsrelease-wporg.sh.plugin-nameinput (defaults to the repository name) for repos where the WP.org slug differs.release/<plugin-name>directory is missing. For the existing cases, the repo names should match, but this could become useful in the future.retention-days: 1to the release artifact upload inreusable-release.yml, since these artifacts are only needed as transitory glue between the release and WP.org release jobs within the same workflow run.Consuming PRs: