WIP - Using core terminus command to wait for Next.js deployment#10009
Draft
stevector wants to merge 4 commits into
Draft
WIP - Using core terminus command to wait for Next.js deployment#10009stevector wants to merge 4 commits into
stevector wants to merge 4 commits into
Conversation
|
Successfully created multidev environment: pr-10009 |
|
Successfully created multidev environment: pr-10009 |
|
Successfully created multidev environment: pr-10009 |
|
Successfully created multidev environment: pr-10009 |
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
1 participant
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.
Once there is a 4.2.0 release of Terminus that includes this command we should be able to simplify the way our GitHub Actions wait for deployment of a given change to rely on Terminus core.