Skip to content

fix(docs): missing Render's Blueprint setup guide links for both v6/v7 "Deploy to Render" docs#7916

Open
Hephaest wants to merge 1 commit into
prisma:mainfrom
Hephaest:prisma-client
Open

fix(docs): missing Render's Blueprint setup guide links for both v6/v7 "Deploy to Render" docs#7916
Hephaest wants to merge 1 commit into
prisma:mainfrom
Hephaest:prisma-client

Conversation

@Hephaest
Copy link
Copy Markdown
Contributor

@Hephaest Hephaest commented May 24, 2026

Backgrounds

Hi Team:)

I have read ORM > Traditional > Deploy to Render doc today and found out there was a missing link:
image

This issue happens on both v6/v7 docs and it should be a quick fix.

PS: I have browsed the Render official docs and I think the original author might referred to this link actually 👉🏼 https://render.com/docs/infrastructure-as-code#setup

Feel free to merge this PR and let me know if there anything I can help with 🤝🏼

Summary by CodeRabbit

  • Documentation
    • Updated and corrected Render deployment documentation by fixing incomplete and malformed Blueprint setup guide references and links. Enhanced accuracy and clarity of link text across multiple documentation versions, providing users with significantly improved navigation and clearer guidance when implementing, configuring, and deploying Infrastructure as Code applications on the Render platform.

Review Change Stack

@vercel
Copy link
Copy Markdown

vercel Bot commented May 24, 2026

@Hephaest is attempting to deploy a commit to the Prisma Team on Vercel.

A member of the Team first needs to authorize it.

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented May 24, 2026

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 9fba74e2-a67c-41a8-9267-f3ea995fcef2

📥 Commits

Reviewing files that changed from the base of the PR and between 9cda317 and f21ff5d.

📒 Files selected for processing (2)
  • apps/docs/content/docs/orm/prisma-client/deployment/traditional/deploy-to-render.mdx
  • apps/docs/content/docs/orm/v6/prisma-client/deployment/traditional/deploy-to-render.mdx

Walkthrough

This PR fixes broken Markdown link references in the Render deployment guides. Both the current and v6 documentation versions have their Infrastructure as Code setup sections corrected to reference Render's Blueprint setup guide with proper link syntax and complete sentence structure pointing to render.yaml examples.

Changes

Render Blueprint Documentation Updates

Layer / File(s) Summary
Render Blueprint deployment guide link corrections
apps/docs/content/docs/orm/prisma-client/deployment/traditional/deploy-to-render.mdx, apps/docs/content/docs/orm/v6/prisma-client/deployment/traditional/deploy-to-render.mdx
The Infrastructure as Code section in both the main and v6 Render deployment guides is corrected to fix the Blueprint setup guide link with proper text and anchor (infrastructure-as-code#setup), and the sentence structure is made complete.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title accurately describes the main change: fixing missing or incorrect Blueprint setup guide links in the Render deployment documentation for multiple versions.
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.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

Warning

There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure.

🔧 ESLint

If the error stems from missing dependencies, add them to the package.json file. For unrecoverable errors (e.g., due to private dependencies), disable the tool in the CodeRabbit configuration.

ESLint skipped: no ESLint configuration detected in root package.json. To enable, add eslint to devDependencies.


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 and usage tips.

@Hephaest Hephaest changed the title fix(blog): missing Render's Blueprint setup guide links for all doc versions fix(docs): missing Render's Blueprint setup guide links for both v6/v7 "Deploy to Render" docs May 24, 2026
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