Combine docker-publish and trigger-redeploy CI workflows #2504
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
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.
In #2493 and #2496 I tried without success to set up a Github Action that would run when a new container image for maproulette-frontend is published to GHCR (the workflow would send a webhook to the Github API to trigger the deployment workflow in the maproulette-deploy repo).
This PR should (hopefully) succeed where those attempts did not, by just adding the webhook to the end of the existing docker-publish workflow (as mentioned in my comment in #2496).
I plan to merge this without review (in order to test it) since it may need further iteration. Sorry for the PR noise.