blog: cross-link Prisma Next posts to the /orm/next docs#8049
Merged
Conversation
Add contextual documentation links across the ten Prisma Next blog posts, so readers can jump from a concept mentioned in a post to the page that covers it. Links land on the first natural mention of each concept and point at the specific doc page (contracts, fundamentals, data modeling, migrations and the migration graph, middleware, extensions, references, quickstart, and coding-agent skills). No prose was rewritten; only link syntax was added around existing words. Posts updated: the-next-evolution-of-prisma-orm, prisma-next-early-access, prisma-next-performance-benchmark, prisma-next-roadmap, prisma-next-roadmap-april-milestone, typescript-migrations-in-prisma-next, data-migrations-in-prisma-next, rethinking-database-migrations, prisma-next-call-for-extension-authors, mongodb-without-compromise. All 23 unique target URLs verified against live docs frontmatter. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
WalkthroughThis PR updates prose across ten Prisma Next and MongoDB blog articles, primarily adding inline documentation hyperlinks to previously plain-text terms (e.g., migrations, query builder, middleware, contracts, extensions) and making minor wording/reflow adjustments. No code examples, embedded components, or exported entities are changed. ChangesBlog content link updates
Estimated code review effort: 1 (Trivial) | ~5 minutes Possibly related PRs
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
Comment |
|
The latest updates on your projects. Learn more about Argos notifications ↗︎
|
![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/blog/content/blog/typescript-migrations-in-prisma-next/index.mdx`:
- Around line 210-217: The workflow step in the blog post incorrectly tells
readers to run ./migration.ts, which is not a valid runnable command in this
context. Update the “Your development workflow becomes” list so the rerun step
references the actual migration runner command used elsewhere in the article,
keeping it consistent with the surrounding migration plan/apply guidance and the
migration.ts mention as the script to edit rather than execute directly.
🪄 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: d558578e-21bd-4802-8aed-4bccd1df0f7b
📒 Files selected for processing (10)
apps/blog/content/blog/data-migrations-in-prisma-next/index.mdxapps/blog/content/blog/mongodb-without-compromise/index.mdxapps/blog/content/blog/prisma-next-call-for-extension-authors/index.mdxapps/blog/content/blog/prisma-next-early-access-write-your-contract-prompt-your-agent-ship-your-app/index.mdxapps/blog/content/blog/prisma-next-performance-benchmark/index.mdxapps/blog/content/blog/prisma-next-roadmap-april-milestone/index.mdxapps/blog/content/blog/prisma-next-roadmap/index.mdxapps/blog/content/blog/rethinking-database-migrations/index.mdxapps/blog/content/blog/the-next-evolution-of-prisma-orm/index.mdxapps/blog/content/blog/typescript-migrations-in-prisma-next/index.mdx
Comment on lines
+210
to
+217
| **[Re-running is safe](https://www.prisma.io/docs/orm/next/migrations/rollbacks-and-recovery).** Before running each operation, the migration runner first evaluates that operation's postcheck. If the postcheck is already true, the runner skips the operation (which makes each operation idempotent). The migration then continues at the first step that hasn't succeeded yet. There's no commenting out lines, no manually unwinding state, and no guessing what's been applied. The single most uncomfortable problem with SQL migrations is solved. | ||
|
|
||
| **Your development workflow becomes:** | ||
|
|
||
| 1. Edit your `contract.prisma` | ||
| 2. Plan a migration: `migration plan` | ||
| 3. Edit the TypeScript and run `./migration.ts` | ||
| 4. Apply the migration: `prisma-next migrate` | ||
| 4. [Apply the migration](https://www.prisma.io/docs/orm/next/migrations/applying-a-migration): `prisma-next migrate` |
Contributor
There was a problem hiding this comment.
🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win
Fix the rerun instruction.
./migration.ts is not a runnable command here; readers will hit a shell error. This workflow step should refer to the migration command itself (or otherwise match the surrounding rerun guidance).
🤖 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/blog/content/blog/typescript-migrations-in-prisma-next/index.mdx` around
lines 210 - 217, The workflow step in the blog post incorrectly tells readers to
run ./migration.ts, which is not a valid runnable command in this context.
Update the “Your development workflow becomes” list so the rerun step references
the actual migration runner command used elsewhere in the article, keeping it
consistent with the surrounding migration plan/apply guidance and the
migration.ts mention as the script to edit rather than execute directly.
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
1 participant
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.
What
Adds contextual documentation cross-links to all ten Prisma Next blog posts. Where a post mentions a concept that now has a docs page (contracts, fundamentals, data modeling, migrations, the migration graph, middleware, extensions, references), the first natural mention is linked to that page.
Why
The
/orm/nextdocs shipped after most of these posts were written, so the posts had almost no links into the docs. Readers who land on a launch, benchmark, or migrations post now have a direct path to the reference material.How links were chosen
Posts updated (link count)
Validation
url:frontmatter onmain.🤖 Generated with Claude Code
Summary by CodeRabbit