chore(ci): purge staging from workflows + env examples - #675
Conversation
Staging is retired (dev -> beta -> main). Remaining references were stale:
- ci.yml / prisma-migrate.yml: drop 'staging' from PR/push branch triggers
- prisma-migrate.yml: remove staging -> 'staging' GitHub Environment mapping
- promotion-guard.yml: fix illustrative fork example ('staging <- dev' -> 'beta <- dev')
- .env.example (backend+web): TEST keys now cover local/dev/beta (beta is a
disposable rehearsal on sandbox payments); LIVE keys are production-only
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Review or Edit in CodeSandboxOpen the branch in Web Editor • VS Code • Insiders |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (5)
📝 WalkthroughWalkthroughThe PR removes ChangesEnvironment ladder update
Possibly related PRs
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Rides #675 (staging-string purge) + latest dev up to `beta`. Head is `dev` so the required `guard` check passes (`[beta]=dev`). Will read **BEHIND** until the "Require branches to be up to date before merging" toggle is removed from the beta ruleset — see the promotion-ladder note; that up-to-date coupling is incompatible with guard's head-must-be-dev rule for a merge-based ladder. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
Final rung — rides #675 (staging-string purge) + latest up to `main`. - Head is `beta` → required `guard` passes (`[main]=beta`). - Up-to-date coupling removed, so no BEHIND block. - 0 conflicts. After this merges, the staging purge is on all three tiers and the whole dev→beta→main ladder is fully synced and enforced. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
What
Removes the last stale
stagingreferences now that the ladder isdev → beta → mainand staging is being deleted everywhere.Changes
stagingfrom branch triggers →[dev, beta, main]staging → 'staging'GitHub Environment mapping'staging <- dev'→'beta <- dev'); the logic was already de-staged in chore(ci,docs): retire staging — dev→beta→main ladder + beta-first self-host plan #670Note
The only remaining
stagingmention is the intentional "Staging was dropped —" historical note in the guard header, which documents the decision.🤖 Generated with Claude Code
Summary by CodeRabbit
Chores
dev → beta → mainpromotion path.stagingfrom automated pull request and migration triggers.Documentation