feat(auth): add Clerk accounts - #49
Merged
Merged
Conversation
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
avatarneil
force-pushed
the
feat/clerk-auth
branch
from
September 13, 2026 23:28
9eab5ca to
52273e8
Compare
Owner
Author
Merge activity
|
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.
Add Clerk account creation, sign-in, and profile controls to the existing bracket.build header, with dedicated auth pages styled to match the dark shadcn theme. Guests can continue using schedules and brackets; saved brackets remain browser-local.
Configure the Next.js 16 proxy and Clerk provider, document setup, and supply Clerk development credentials to CI through GitHub Actions secrets. Archive the Next.js build for artifact transfer because Turbopack emits colon-containing filenames that GitHub rejects individually. Production hosting keys must use the production Clerk instance.
Validation: production build and TypeScript passed; lint passed with eight existing warnings. Browser checks covered sign-in/sign-up navigation, mobile/laptop/ultrawide layouts, and 16px mobile auth inputs. The owner completed a development signup and confirmed the signed-in profile appeared.
Production rollout: the owner has configured hosting keys. Clerk CLI still reports DNS/SSL/email and social-provider setup pending; complete those settings before expecting production sign-in to work.