fix: exclude main branch from preview site URL - #2466
Merged
Conversation
✅ Deploy Preview for astro-www-2 ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Deploying with
|
| Status | Name | Latest Commit | Updated (UTC) |
|---|---|---|---|
| ✅ Deployment successful! View logs |
astro-build | 06ffbc1 | Jun 12 2026, 05:24 PM |
🚀 Deploying Preview to Cloudflare 🚀Preview URL: https://fix-preview-site-main-branch.previews.astro.build (commit 06ffbc1)This URL reflects your latest Preview deploymentPreview Deployments by commit
|
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
1 participant
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.
On Cloudflare Workers Builds,
WORKERS_CI_BRANCHis set to the branch name even onmain, which caused the site URL to be overridden tomain.previews.astro.buildinstead ofastro.build.This adds a check to exclude
mainfrom preview site URL generation so production deploys use the correct site URL.Fixes the issue noted in #2432 (comment)