Repository navigation
Conversation
coder13
marked this pull request as ready for review
November 3, 2026 14:42
✅ Deploy Preview for competition-groups ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
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.
Summary
Deploy the current
betabranch to production by merging it intomain.Scope: PR #95, WCIF v2 migration, UAT fixes and dual-round support. The tested source tree is unchanged (
2a1d23b6e33af18572db0a9f5127924e96b3acbd).Compare: main...beta
Commits
Validation
PR #95 head passed GitHub Test, Lint, Type Check and Netlify preview. Local validation passed 47 suites / 238 tests / 2 snapshots, TypeScript, lint, production build and Storybook. Public preview regressions covered 15 competition home pages plus focused FMC, blind seed, dual round, navigation and results checks.
Created directly through the GitHub connector because workflow dispatch is unavailable in that connector and the browser is signed out. This reproduces the existing Deploy workflow's release-PR operation without changing the beta-to-main release path.