ci: Split deploy-db-migration into per-env jobs so the inactive env shows skipped#242
Merged
Merged
Conversation
rgibert
approved these changes
Jun 5, 2026
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
2 participants
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.
Splits the single matrix-based deploy-db-migration job into separate deploy-db-migration-test and deploy-db-migration-prod jobs, each gated by a job-level if: that mirrors the existing deploy-test/deploy-prod conditions, and rewires the deploy jobs' needs: to the matching per-env migration. This is a behavioral no-op: the same migrations and deploys run against the same environments under the same trigger conditions. The only change is that the non-targeted environment's migration job now reports as skipped instead of a misleading green success (where the job ran but every step was individually if-skipped), which previously read like the inactive env had migrated when it had not.
Tested here looking good.