Fix dev-deploy.yml: deploy triggering commit instead of tip of dev branch#58
Draft
Copilot wants to merge 2 commits into
Draft
Fix dev-deploy.yml: deploy triggering commit instead of tip of dev branch#58Copilot wants to merge 2 commits into
Copilot wants to merge 2 commits into
Conversation
Copilot
AI
changed the title
[WIP] Fix dev-deploy workflow to use dev branch instead of main
Fix dev-deploy.yml: deploy triggering commit instead of tip of dev branch
Jun 28, 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
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.
dev-deploy.ymlwas hardcodingref: dev, causing it to always build and push whatever was at the current tip ofdev— not the specific commit that passed CI. This creates a race condition where newer, untested commits get deployed.Change
dev-deploy.yml: Replaceref: devwithref: ${{ github.event.workflow_run.head_sha }}— the same patternprod-deploy.ymlalready uses correctly.github.event.workflow_run.head_shais the exact commit SHA that triggered the upstream CI workflow, so the deployed image will always correspond to the code that was actually tested.