content(blog): add Prisma Next April milestone roadmap post#7895
Closed
ankur-arch wants to merge 9 commits into
Closed
content(blog): add Prisma Next April milestone roadmap post#7895ankur-arch wants to merge 9 commits into
ankur-arch wants to merge 9 commits into
Conversation
Adds the new "Prisma Next: April milestone complete" article and its hero/meta images, refreshes hero/meta assets across related Prisma Next blog posts, and ignores the locally cloned prisma-next repo so it can't be accidentally added as a gitlink. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
WalkthroughThis PR adds a simple local development exclusion to Changes.gitignore Configuration
Prisma Next April Milestone Blog Post
Estimated code review effort🎯 2 (Simple) | ⏱️ ~12 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.
🧹 Nitpick comments (1)
.gitignore (1)
45-45: ⚡ Quick winAnchor the ignore rule to repository root
If this is only for a root-level local clone, use
/prisma-next/to avoid unintentionally ignoring similarly named nested directories later.[Line 45]
Proposed change
-prisma-next/ +/prisma-next/🤖 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 @.gitignore at line 45, The .gitignore entry "prisma-next/" should be anchored to the repository root to avoid ignoring same-named nested folders; update the entry to "/prisma-next/" in the .gitignore so the ignore rule applies only to the top-level prisma-next directory.
🤖 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.
Nitpick comments:
In @.gitignore:
- Line 45: The .gitignore entry "prisma-next/" should be anchored to the
repository root to avoid ignoring same-named nested folders; update the entry to
"/prisma-next/" in the .gitignore so the ignore rule applies only to the
top-level prisma-next directory.
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
Run ID: 27fa63f9-918d-4582-bd6b-5b896df3cfe4
⛔ Files ignored due to path filters (10)
apps/blog/public/data-migrations-in-prisma-next/imgs/hero.svgis excluded by!**/*.svgapps/blog/public/data-migrations-in-prisma-next/imgs/meta.pngis excluded by!**/*.pngapps/blog/public/mongodb-without-compromise/imgs/hero.svgis excluded by!**/*.svgapps/blog/public/mongodb-without-compromise/imgs/meta.pngis excluded by!**/*.pngapps/blog/public/prisma-next-call-for-extension-authors/imgs/hero.svgis excluded by!**/*.svgapps/blog/public/prisma-next-call-for-extension-authors/imgs/meta.pngis excluded by!**/*.pngapps/blog/public/prisma-next-roadmap-april-milestone/imgs/hero.svgis excluded by!**/*.svgapps/blog/public/prisma-next-roadmap-april-milestone/imgs/meta.pngis excluded by!**/*.pngapps/blog/public/the-next-evolution-of-prisma-orm/imgs/hero-61773d2cc286213d32b63e59605b0f5e0df4fe52-844x474-cb41e2fab7.svgis excluded by!**/*.svgapps/blog/public/the-next-evolution-of-prisma-orm/imgs/meta-558fe7eccfd12d3b52c325d62e5fa463a1b5f619-1200x640-3212708663.pngis excluded by!**/*.png
📒 Files selected for processing (2)
.gitignoreapps/blog/content/blog/prisma-next-roadmap-april-milestone/index.mdx
|
The latest updates on your projects. Learn more about Argos notifications ↗︎
|
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.
Adds the new "Prisma Next: April milestone complete" article and its hero/meta
images, refreshes hero/meta assets across related Prisma Next blog posts, and
ignores the locally cloned prisma-next repo so it can't be accidentally added
as a gitlink.
Co-Authored-By: Claude Opus 4.7 (1M context) noreply@anthropic.com
Summary by CodeRabbit
Documentation
Chores