Repository navigation
docs(compute): coding-assistant previews, environments page title, FAQ entry - #8454
Conversation
…itle, FAQ entry - deploy-on-push: "If a coding assistant is building the feature" section (feature branch, default-branch protection, enrolled agent credential, preview URL from the deploy report), description and meta description mention a coding assistant, Next steps link uses the new page title. - branching: title and meta title become "Environments: production, staging and preview branches"; new "Preview vs staging environments" table. - faq: "Can my coding assistant deploy a test version without touching production?" entry; "What's a branch?" links the Environments docs. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…ault policy Frontmatter only: title and meta title. The body is unchanged. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info
WalkthroughThe docs now describe preview, staging, and production environments and explain how coding assistants use preview branches. They also document database behavior, default-branch deployment, branch protection, and enrolled agents’ Prisma credentials. ChangesCompute environment documentation
Priority: ⬇️ Low Estimated code review effort: 2 (Simple) | ~10 minutes Change: Other Suggested reviewers: Merge Risk: ⚪ Minimal · up to No actionable documentation issue is established in the supplied review context. The author reports that the documentation checks passed, so the mergeability risk is minimal. Pre-merge checks |
 |
| Check name | Status | Explanation |
|---|---|---|
| Description Check |  |
Check skipped - CodeRabbit’s high-level summary is enabled. |
| Title check | |
The title clearly summarizes the main documentation changes: coding-assistant previews, the environments page, and the FAQ entry. |
| Docstring Coverage | |
No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0… |
| 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. |
✨ 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
Comment @coderabbitai help to get the list of available commands.
🍈 Lychee Link Check Report161 links: ✅ All links are working!Full Statistics Table
|
|
@coderabbitai review |
|
|
@coderabbitai review |
✅ Action performedReview finished.
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
This branch was successfully deployed
1 participant
These four Prisma Compute docs pages explain how to host a test version of an app, including a feature a coding assistant is building, as a preview or staging environment without replacing production.
Changes
apps/docs/content/docs/compute/deploy-on-push.mdxDATABASE_URLcaveat is repeated. It says a push to the default branch deploys production without asking, links GitHub's "About protected branches" page, links agent enrollment (an enrolled agent works on preview branches and asks before changing production through the Prisma API), and says that policy does not cover the deploy workflow. It ends with the preview URL in the deploy report, merge, and teardown.descriptionandmetaDescriptionname a coding assistant./compute/branchingnow uses that page's new title.apps/docs/content/docs/compute/branching.mdx(URL kept)title: "Environments: production, staging and preview branches";metaTitle: the same plus " | Prisma Compute".DATABASE_URLcaveat, and one sentence onnpx prisma deploy module.ts --stage stagingwithout GitHub.apps/docs/content/docs/compute/faq.mdxapps/docs/content/docs/(index)/prisma-compute/agent-enrollment.mdx(its own commit)title"Enroll your coding agent: it works on preview branches and asks before changing production";metaTitle"Enroll a coding agent: works on previews, asks before production" (64 characters).description,metaTitleandmetaDescription, so whichever merges second gets a small frontmatter conflict. Resolution: keep feat(docs): guide agent enrollment through MCP #8369'sdescription,metaDescriptionand body, and this PR'stitleandmetaTitle. feat(docs): guide agent enrollment through MCP #8369's body keeps the default policy table and the default-branch push warning that the new title relies on.These docs pages have no Updated field or update history, so no date line was added.
Sources checked 2026-10-12
--stage stagingwithout GitHub.Checks run locally
pnpm --filter docs test: 76 of 76 pass.pnpm --filter docs lint:links: 0 errors.check-ai-signs.shon the four files: clean.pnpm --filter docs build, thenstarton port 3001: all four pages return 200 with the new<title>, meta description and H1, the canonical URLs are the same as before, and each.mdURL renders the new sections.🤖 Generated with Claude Code
Summary by CodeRabbit
DATABASE_URL.