refine: make billing section more discoverable#7869
Open
ankur-arch wants to merge 2 commits intomainfrom
Open
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
🍈 Lychee Link Check Report377 links: ✅ All links are working!Full Statistics Table
|
Contributor
WalkthroughA set of documentation edits across the docs site: new "Billing and pricing" section for Prisma Postgres on Vercel, multiple typo and wording fixes, added examples and Prisma Client extension samples (SafeQL, Neon adapter, Deno Deploy snippet), an AI-safety consent addition to the CLI reference, and a large cspell wordlist expansion. No runtime code changes. ChangesDocs content, examples, and guidance (multiple pages)
Spell-check dictionary update
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~25 minutes 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@apps/docs/content/docs/guides/postgres/vercel.mdx`:
- Around line 64-69: The spellcheck CI is failing for the changes under the "##
Billing and pricing" section: either correct the flagged spelling/terminology in
the text (e.g., within the "Prisma Postgres" / "Vercel Marketplace" mentions and
the FAQ link text) or add any valid product terms that the linter flags to the
project spellcheck dictionary so lint:spellcheck passes; update the content
string accordingly and commit the dictionary entry if you choose the whitelist
approach.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
Run ID: ccf343f4-4bc5-4520-80cc-75bacdc0dd5a
📒 Files selected for processing (2)
apps/docs/content/docs/guides/postgres/vercel.mdxapps/docs/content/docs/postgres/faq.mdx
Comment on lines
+64
to
+69
| ## Billing and pricing | ||
|
|
||
| Prisma Postgres uses [usage-based pricing](https://www.prisma.io/pricing) based on operations and storage. The same plans and rates apply when you create a database via the Vercel Marketplace, and your Prisma Postgres usage is billed through your Vercel account. | ||
|
|
||
| To change your plan, see [How do I upgrade my plan if I am using Prisma Postgres via Vercel?](/postgres/faq#how-do-i-upgrade-my-plan-if-i-am-using-prisma-postgres-via-vercel) in the Prisma Postgres FAQ. | ||
|
|
Contributor
There was a problem hiding this comment.
Resolve the spellcheck blocker before merge.
GitHub Actions shows lint:spellcheck failing for this PR; please fix the flagged term(s) in this docs update or add valid product terms to the project dictionary so CI can pass.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@apps/docs/content/docs/guides/postgres/vercel.mdx` around lines 64 - 69, The
spellcheck CI is failing for the changes under the "## Billing and pricing"
section: either correct the flagged spelling/terminology in the text (e.g.,
within the "Prisma Postgres" / "Vercel Marketplace" mentions and the FAQ link
text) or add any valid product terms that the linter flags to the project
spellcheck dictionary so lint:spellcheck passes; update the content string
accordingly and commit the dictionary entry if you choose the whitelist
approach.
|
The latest updates on your projects. Learn more about Argos notifications ↗︎
|
aidankmcalister
previously approved these changes
May 5, 2026
Contributor
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@apps/docs/content/docs/orm/v6/prisma-client/using-raw-sql/safeql.mdx`:
- Line 320: Update the inline comment "// Query for closest points of interests"
to correct grammar: change "points of interests" to "points of interest" so the
comment reads "// Query for closest points of interest"; this is the comment
near the SQL/geospatial query in the safeql.mdx snippet and should be updated
where that exact comment string appears.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
Run ID: 84e1b9c2-3618-4907-9d0e-06b39275d4ce
📒 Files selected for processing (12)
apps/docs/content/docs/orm/v6/more/ai-tools/tabnine.mdxapps/docs/content/docs/orm/v6/more/dev-environment/environment-variables.mdxapps/docs/content/docs/orm/v6/overview/databases/neon.mdxapps/docs/content/docs/orm/v6/prisma-client/deployment/edge/deploy-to-deno-deploy.mdxapps/docs/content/docs/orm/v6/prisma-client/deployment/serverless/deploy-to-vercel.mdxapps/docs/content/docs/orm/v6/prisma-client/queries/query-optimization-performance.mdxapps/docs/content/docs/orm/v6/prisma-client/queries/transactions.mdxapps/docs/content/docs/orm/v6/prisma-client/using-raw-sql/raw-queries.mdxapps/docs/content/docs/orm/v6/prisma-client/using-raw-sql/safeql.mdxapps/docs/content/docs/orm/v6/reference/prisma-cli-reference.mdxapps/docs/content/docs/orm/v6/reference/prisma-client-reference.mdxapps/docs/cspell.json
✅ Files skipped from review due to trivial changes (4)
- apps/docs/content/docs/orm/v6/prisma-client/using-raw-sql/raw-queries.mdx
- apps/docs/content/docs/orm/v6/more/ai-tools/tabnine.mdx
- apps/docs/content/docs/orm/v6/reference/prisma-client-reference.mdx
- apps/docs/content/docs/orm/v6/more/dev-environment/environment-variables.mdx
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary by CodeRabbit