Repository navigation
ci: prepare master-to-v12 docs branch rename - #1464
Merged
Merged
Conversation
Derive production deployment routing and Lighthouse baseline environments from the repository default branch. Accept pushes to both master and v12 so deployment works across the rename, and cover production and manual preview behavior before and after it. Signed-off-by: Florian Hammerschmidt <florianh89@gmail.com>
Contributor
Contributor
Lighthouse baselineCompared with target branch
Download the full Lighthouse reports and baseline Commit |
jderochervlk
approved these changes
Oct 21, 2026
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
guide | fd635af | Commit Preview URL Branch Preview URL |
Oct 21 2026, 03:41 PM |
This branch was successfully deployed
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.
Renaming the website's default branch from
mastertov12currently stops push deployments and leaves production routing and Lighthouse baselines tied to the old name.Use the repository's default branch for docs and guide production routing, pass that branch into Lighthouse artifact selection, and accept pushes to both
masterandv12during the transition. Existing production behavior and isolated manual previews continue to work before the rename.After merging:
mastertov12, keepingv12as the default.production_branchtov12, update any deployment hooks that targetmaster, and run a production deployment.Before any later default-branch switch, the compiler's
maintenance/12.xpublication workflow must explicitly target websitev12. The compiler v13 follow-up targetsv13through rescript-lang/rescript#8753.This PR prepares the rename; it does not rename branches or change Cloudflare settings.