feat(blog): add new migrations blog#7672
Merged
mhartington merged 3 commits intomainfrom Mar 27, 2026
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
✅ Files skipped from review due to trivial changes (1)
WalkthroughAdds a new MDX blog post introducing the "Prisma Next migrations" model, detailing Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes 🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. 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. 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: 2
🧹 Nitpick comments (1)
apps/blog/content/blog/rethinking-database-migrations/index.mdx (1)
20-20: Consider varying repeated phrasing for tighter prose.“You've probably...” appears in close proximity twice; swapping one instance for a different lead-in would improve rhythm.
Also applies to: 34-34
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@apps/blog/content/blog/rethinking-database-migrations/index.mdx` at line 20, The two nearby sentences both start with "You've probably..."; replace one instance (either the earlier "If you've written migrations before, you've probably seen something like this:" or the later occurrence at the noted nearby line) with an alternative lead-in such as "If you've worked with migrations before..." or "Chances are you've encountered..." to avoid repetition and tighten the prose while keeping the same meaning.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@apps/blog/content/blog/rethinking-database-migrations/index.mdx`:
- Line 182: Update the Markdown link URL for the Discord invite so it uses HTTPS
instead of HTTP: change the link target
"http://pris.ly/discord?utm_campaign=prisma-next" to
"https://pris.ly/discord?utm_campaign=prisma-next" for the line containing the
"#prisma-next" Discord link so external links remain secure.
- Around line 77-83: The fenced code block labeled "json" contains
JavaScript-style comments which are invalid JSON; update that fenced block by
either changing the language tag from `json` to `jsonc` (so comments are
allowed) or removing the `// ...` inline comments from the object so it becomes
valid JSON; locate the fenced snippet containing the keys "from", "to", and
"description" and apply the chosen fix.
---
Nitpick comments:
In `@apps/blog/content/blog/rethinking-database-migrations/index.mdx`:
- Line 20: The two nearby sentences both start with "You've probably...";
replace one instance (either the earlier "If you've written migrations before,
you've probably seen something like this:" or the later occurrence at the noted
nearby line) with an alternative lead-in such as "If you've worked with
migrations before..." or "Chances are you've encountered..." to avoid repetition
and tighten the prose while keeping the same meaning.
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
Run ID: 3af6578d-4bc4-47ed-8593-ee5ef5f9c842
⛔ Files ignored due to path filters (3)
apps/blog/public/rethinking-database-migrations/imgs/hero.pngis excluded by!**/*.pngapps/blog/public/rethinking-database-migrations/imgs/hero.svgis excluded by!**/*.svgapps/blog/public/rethinking-database-migrations/imgs/meta.pngis excluded by!**/*.png
📒 Files selected for processing (1)
apps/blog/content/blog/rethinking-database-migrations/index.mdx
apps/blog/content/blog/rethinking-database-migrations/index.mdx
Outdated
Show resolved
Hide resolved
apps/blog/content/blog/rethinking-database-migrations/index.mdx
Outdated
Show resolved
Hide resolved
Align the new migrations article with review feedback by using jsonc for commented snippets, securing the Discord link with https, and tightening repeated phrasing. Made-with: Cursor
mhartington
force-pushed
the
migrations-blog
branch
from
7b27c11 to
6e3a3d9
Compare
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.
Summary by CodeRabbit