Prevent CHANGELOG.md from triggering staging deploy #1699
Merged
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
After #1679, the staging deploy that occurs during a release merge gets interrupted by a second staging deploy triggered by `auto`'s push to master containing the updated `CHANGELOG.md`. This PR prevents that second deploy from running, avoiding a spurious deploy failure that happens when the first deploy is canceled.
mvandenburgh
approved these changes
Oct 5, 2023
jjnesbitt
approved these changes
Oct 5, 2023
|
🚀 PR was released in |
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.
After #1679, the staging deploy that occurs during a release merge gets interrupted by a second staging deploy triggered by
auto's push to master containing the updatedCHANGELOG.md.This PR prevents that second deploy from running, avoiding a spurious deploy failure that happens when the first deploy is canceled.
Thanks to @mvandenburgh for helping me debug this problem.