Fix CI HTML preview naming conflict with Netlify deploy-preview mechanism #608
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.
The CI workflow was using Netlify deployment names that conflict with Netlify's built-in deploy-preview mechanism, causing HTML previews to not show the latest build correctly.
Problem
Netlify was showing this warning during deployments:
The CI workflow in
.github/workflows/ci.ymlwas using:This naming pattern conflicts with Netlify's internal deploy-preview system, preventing the latest HTML builds from being properly displayed on PR preview links.
Solution
Changed the naming structure to avoid the conflict:
--context deploy-preview→--context pr-preview--alias deploy-preview-${{ github.event.pull_request.number }}→--alias pr-${{ github.event.pull_request.number }}Impact
pr-123instead ofdeploy-preview-123devcontext) are unaffectedFixes #607.
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.