Skip to content

chore(ci): purge staging from workflows + env examples - #675

Merged
onerandomdevv merged 1 commit into
devfrom
chore/purge-staging-refs
Jul 28, 2026
Merged

chore(ci): purge staging from workflows + env examples#675
onerandomdevv merged 1 commit into
devfrom
chore/purge-staging-refs

Conversation

@onerandomdevv

@onerandomdevv onerandomdevv commented Jul 28, 2026

Copy link
Copy Markdown
Collaborator

What

Removes the last stale staging references now that the ladder is dev → beta → main and staging is being deleted everywhere.

Changes

  • ci.yml / prisma-migrate.yml — drop staging from branch triggers → [dev, beta, main]
  • prisma-migrate.yml — remove the staging → 'staging' GitHub Environment mapping
  • promotion-guard.yml — fix the illustrative fork-guard example ('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 #670
  • apps/backend/.env.example, apps/web/.env.example — payment-key guidance: TEST keys now cover local/dev/beta (beta is a disposable rehearsal on sandbox payments); LIVE keys are production-only (previously mislabelled beta as LIVE)

Note

The only remaining staging mention is the intentional "Staging was dropped —" historical note in the guard header, which documents the decision.

🤖 Generated with Claude Code

Summary by CodeRabbit

  • Chores

    • Updated deployment workflows to use the dev → beta → main promotion path.
    • Removed staging from automated pull request and migration triggers.
    • Updated environment selection for development, beta, and production deployments.
  • Documentation

    • Clarified CORS configuration guidance.
    • Updated Paystack key instructions for local, development, beta, and production environments.

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>
@vercel

vercel Bot commented Jul 28, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
twizrr-admin Ready Ready Preview, Comment Jul 28, 2026 5:41pm
twizrr-app Ready Ready Preview, Comment Jul 28, 2026 5:41pm
twizrr-web Ready Ready Preview, Comment Jul 28, 2026 5:41pm

@codesandbox

codesandbox Bot commented Jul 28, 2026

Copy link
Copy Markdown

Review or Edit in CodeSandbox

Open the branch in Web EditorVS CodeInsiders

Open Preview

@coderabbitai

coderabbitai Bot commented Jul 28, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 68a6b2b9-bdff-4244-8a1b-81f99e378115

📥 Commits

Reviewing files that changed from the base of the PR and between d09777a and 3a5f868.

📒 Files selected for processing (5)
  • .github/workflows/ci.yml
  • .github/workflows/prisma-migrate.yml
  • .github/workflows/promotion-guard.yml
  • apps/backend/.env.example
  • apps/web/.env.example

📝 Walkthrough

Walkthrough

The PR removes staging from CI and Prisma migration triggers, maps non-production workflow refs to development, updates the promotion ladder comment to dev -> beta -> main, and revises backend and web environment guidance to reference beta.

Changes

Environment ladder update

Layer / File(s) Summary
Workflow branch and environment routing
.github/workflows/ci.yml, .github/workflows/prisma-migrate.yml, .github/workflows/promotion-guard.yml
CI and migration workflows no longer trigger for staging; migration environments map main to production, beta to beta, and other refs to development.
Environment configuration guidance
apps/backend/.env.example, apps/web/.env.example
CORS and Paystack key comments now describe beta instead of staging.
Estimated code review effort: 1 (Trivial) ~5 minutes

Possibly related PRs

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name Status Explanation Resolution
Description check ⚠️ Warning The description covers the change, but it misses most required template sections like type, area, testing, checklist, screenshots, and reviewer notes. Add the missing template sections, especially type of change, affected area, test steps, pre-commit checklist, screenshots or N/A, and reviewer notes.
✅ Passed checks (4 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly summarizes the main change: removing staging references from CI workflows and env examples.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch chore/purge-staging-refs

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@onerandomdevv
onerandomdevv merged commit 0902fc5 into dev Jul 28, 2026
14 checks passed
@onerandomdevv
onerandomdevv deleted the chore/purge-staging-refs branch July 28, 2026 17:42
onerandomdevv added a commit that referenced this pull request Jul 28, 2026
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)
onerandomdevv added a commit that referenced this pull request Jul 28, 2026
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)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant