Run the new version-check job from the wp-svn orb #130
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
kienstra
commented
Sep 28, 2022
|
Note to self: squash-merge when merging |
dreamwhisper
approved these changes
Oct 4, 2022
|
@dreamwhisper, |
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.
Changes
Run the new check-versions job from the wp-svn orb on tagging a release:
We won't need that job when we're not deploying, so it only runs it then.
As part of my 15Five development goal, not in this sprint 😄
Testing Steps
Not needed. Just make sure nothing looks horribly wrong. If this job goes bad, it'll simply stop the pipeline, it won't do anything else.