Remove unneeded "After deploy" steps in prepare-release.yml file
#2663
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
This is no longer needed because they are now implemented in woocommerce/grow#89.
|
New grow actions released :) This PR should be ready to merge. |
tomalec
approved these changes
Nov 16, 2023
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 proposed in this Pull Request:
In PR woocommerce/grow#89, there is an update to the prepare-release.yml file. This made some of our custom "after deploy" post steps redundant.
In this PR, we remove the custom "after deploy" post steps in our extension repo.
Detailed test instructions:
We can test this in the next release by following the steps here: https://github.com/woocommerce/facebook-for-woocommerce/wiki/Build-&-Release#release-basics
There should not be redundant or duplicated "After deploy" steps.
Additional details: