[gregory-boch-prisma]

This guide explains how to host a test version of an app next to production with previews per branch or pull request, staging, test databases, feature flags and blue-green or canary releases, and how Fly.io, Netlify, Prisma Compute, Railway, Render and Vercel do it.

Changes

• Render and Vercel headings. "Render" and "Vercel" were bare host names, so a reader scanning the page could not tell what each section covers. They are now "Render preview environments and staging" and "Vercel preview deployments and staging". The section text is not edited, and #render and #vercel keep working through explicit heading ids.
• "When a coding assistant builds the feature". The section covered gating the merge with branch protection, but not the deploy that follows it. A new paragraph says that if the production deploy runs as a GitHub Actions job, a GitHub deployment environment with required reviewers, self-reviews prevented and administrator bypass turned off can gate the deploy itself, that the production deploy credentials belong in that environment because a job gets environment secrets only after approval, and that a private repository needs GitHub Enterprise for this, because GitHub Free, Pro and Team offer required reviewers only in public repositories.
• Sources table. The GitHub row gains GitHub's "Deployments and environments" page and the 2026-11-02 check date for that page and for GitHub's plans.
• updatedAt is 2026-11-03, with one line in the update history.

The title, meta title, meta description, excerpt, opening answer, host table, About note and the host section bodies are not edited. No anchor changed.

Sources checked 2026-11-02

• https://docs.github.com/en/actions/reference/workflows-and-actions/deployments-and-environments: "Use required reviewers to require a specific person or team to approve workflow jobs that reference the environment."
• Same page, on how many reviewers it takes: one "needs to approve the job for it to proceed."
• Same page: "If you are on a GitHub Free, GitHub Pro, or GitHub Team plan, required reviewers are only available for public repositories."
• Same page: "users who initiate a deployment cannot approve the deployment job, even if they are a required reviewer"
• Same page: "By default, administrators can bypass the protection rules and force deployments to specific environments."
• Same page: "you can configure environments to disallow bypassing the protection rules for all deployments to the environment."
• Same page: "If the environment requires approval, a job cannot access environment secrets until one of the required reviewers approves it."
• https://docs.github.com/en/get-started/learning-about-github/githubs-plans: "Deployment protection rules with GitHub Actions for private or internal repositories" (listed under GitHub Enterprise)

Checks

• git diff --check: clean.
• Anchors: #render and #vercel are set with the blog's explicit heading id syntax, and no link in the repo points at them from another page.
• Tables: the GitHub row of the sources table keeps its column count.
• Do-not-claim lint on the page diff, repo and diff modes: 0 hits.
• PR text lint on this body and the commit message: 0 hits.
• Claims check: 0 matches, none a claim for Prisma. The new paragraph makes no statement about Prisma.

🤖 Generated with Claude Code

Summary by CodeRabbit

• Documentation
  • Updated the guide with instructions for gating GitHub Actions production deployments using a GitHub deployment environment, including reviewer and credential requirements.
  • Clarified that private repositories require GitHub Enterprise for this setup.
  • Updated the Render and Vercel section headings while preserving their links, and refreshed the article’s update date and source history.

[vercel]

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

Project	Deployment	Actions	Updated
blog	Ready	Preview	Nov 2, 2026 6:55pm UTC
docs	Ready	Preview	Nov 2, 2026 6:55pm UTC
eclipse	Ready	Preview	Nov 2, 2026 6:55pm UTC
site	Ready	Preview	Nov 2, 2026 6:55pm UTC

1 Skipped Deployment

Project	Deployment	Actions	Updated
handbook	Skipped		Nov 2, 2026 6:55pm UTC

[coderabbitai]

No actionable comments were generated in the recent review.

Recent review info

Run configuration

• Source mode: Auto
• Repository: Unavailable
• Branch: Unavailable
• File: No configuration file from this repository applied
• Commit: Unavailable
• Layers: Repository UI
• Review profile: CHILL
• Plan: Essentials
• Run ID: dfd3459e-6865-4005-be93-cb9e536d2b13

Commits

Reviewing files that changed from the base of the PR and between 8f8906a and f400e53.

Files selected for processing: 1

• apps/blog/content/blog/host-a-test-version-without-replacing-production/index.mdx

Included review availability: This review used your included allowance. Your plan provides up to 5 included reviews per hour; 1 remain after this review.

Walkthrough

The article adds guidance for approving GitHub Actions production deployments through deployment environments. It also revises two section headings, updates references and dates, and adds an update-history entry.

Changes

Article update

Layer / File(s)	Summary
Deployment guidance and article updates apps/blog/content/blog/host-a-test-version-without-replacing-production/index.mdx	Adds deployment environment approval requirements and credential guidance, notes the GitHub Enterprise requirement for private repositories, and updates headings, references, and article dates.

Estimated code review effort: 2 (Simple) | ~8 minutes

Suggested reviewers: vanrensbird

Merge Risk: Minimal · up to f400e

The documentation update is mergeable; no confirmed correctness or operational issue remains.

Pre-merge checks: 5

Check name	Status	Explanation
Description Check		Check skipped - CodeRabbit’s high-level summary is enabled.
Title check		The title clearly and specifically summarizes both main changes: descriptive Render and Vercel headings and GitHub deployment environments for production deployments.
Docstring Coverage		No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentat…
Linked Issues check		Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check		Check skipped because no linked issues were found for this pull request.

Full details: Docstring Coverage

Explanation

No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentation-only edits and deletions within surviving functions are included; unchanged diff context and fully deleted functions are excluded. Analyzed 0 functions across 0 files. (1 skipped: 1 unsupported.)

Finishing Touches

Generate unit tests (beta)

• Commit to this branch
• Create a new PR

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts