RELEASES — Live site and blue previews
Adopted 4 Oct 2026 at Ravneet's request; addresses updated 10 Oct 2026. Every AI tool and developer follows this.
The sites
| LIVE | Per-change preview (blue) | |
|---|---|---|
| Address | https://ai.cetking.com (main) and https://cetking-platform.vercel.app (same site, kept live for old links) | Link posted by the Vercel bot on each pull request |
| Who sees it | Students and Google | Ravneet and the team |
| GitHub branch | cetking-one-nextjs |
The change's own branch (blue/...) |
| Changes when | Only after Ravneet says "go live" | On every push to that branch |
- Both live addresses show the same site and both have working OTP and Google login. A login is kept per address, so a student logged in on one is not automatically logged in on the other.
- Ravneet, 10 Oct 2026: keep cetking-platform.vercel.app live for now; testing stays on the per-change
blue previews. (A
testingbranch was created and is not used.) - Same database. Previews and live share the Cetking Learn Supabase: logins, coins and ticks made on a preview are real.
- Vercel keeps every past live version, so the previous live site is always one click away (Vercel → Deployments → previous → Instant Rollback).
How a change goes live
- Branch. Create a new branch from
cetking-one-nextjs(e.g.blue/shabda-page). Never commit site code directly tocetking-one-nextjs. - Build locally if you can. Run
npm run build. It must pass, including the TypeScript check. - Push in one go, then open a pull request into
cetking-one-nextjs. Vercel builds a preview and posts its link on the pull request. Judge only the latest build. - Preview must say Ready. If it says Error, fix it on the same branch.
- Ravneet checks the preview on his phone. Give him the preview link and a short plain-language list of what changed.
- Go live only on his word. When Ravneet says "go live", merge that change's pull request into
cetking-one-nextjs(squash). Vercel rebuilds the live site in 2–5 minutes. - Check live. Open the live pages that changed on https://ai.cetking.com and confirm. Report back in one or two lines.
- If live looks wrong: roll back in Vercel to the previous deployment first, then fix on the branch.
Exceptions
- Docs-only changes (files in
docs/only) may go straight tocetking-one-nextjs. - Emergency fixes still go through a preview, but Ravneet may approve from the preview link at once.
Checklist before asking Ravneet to approve
- Local
npm run buildpassed (or the reason it could not run is stated) - Vercel preview says Ready on the latest commit
- Phone-width check of every page the change touches
- Old links still work (redirects in
next.config.js) - No secrets, no user counts, no real student names (see RULES.md)
History
- 4 Oct 2026 — First release done this way: subject bot lineup (PR #125). The first blue build failed
(missing
@types/react-dom); it was fixed on blue and live was never affected. - 10 Oct 2026 — Live moved to https://ai.cetking.com (PR #179). cetking-platform.vercel.app stays live too (forward removed in PR #181); testing stays on blue previews.