You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
Previously we had the deployment workflow trigger when a build workflow completed. The problem is that the deployment workflow would trigger even if the build workflow failed; GitHub Actions does not provide a way of only triggering a workflow only if the dependent workflow succeeded.
To solve this problem we are reversing the dependency. Instead of the deployment workflow listening for the build workflow to complete, the build workflow will explicitly trigger the deployment workflow, and only when it completes successfully.
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.
Previously we had the deployment workflow trigger when a build workflow completed. The problem is that the deployment workflow would trigger even if the build workflow failed; GitHub Actions does not provide a way of only triggering a workflow only if the dependent workflow succeeded.
To solve this problem we are reversing the dependency. Instead of the deployment workflow listening for the build workflow to complete, the build workflow will explicitly trigger the deployment workflow, and only when it completes successfully.