Skip to content

docs: point Prisma Next repo links at prisma/prisma - #8115

Open
ankur-arch wants to merge 1 commit into
mainfrom
docs/point-links-at-prisma-prisma
Open

docs: point Prisma Next repo links at prisma/prisma#8115
ankur-arch wants to merge 1 commit into
mainfrom
docs/point-links-at-prisma-prisma

Conversation

@ankur-arch

@ankur-arch ankur-arch commented Jul 29, 2026

Copy link
Copy Markdown
Contributor

The Prisma Next codebase moved from prisma/prisma-next to prisma/prisma as its canonical repository, so GitHub links into the old repo are dead. This updates every prisma/prisma-next link in apps/docs:

  • orm/next/migrations/the-migration-graph.mdx: the clone-and-try-it snippet now clones https://github.com/prisma/prisma and the cd step uses the new directory name.
  • orm/next/extensions/using-extensions.mdx: the five extension readme links and the four runnable example links.
  • orm/next/index.mdx: the explore-the-source link.
  • orm/next/migrations/editing-a-migration.mdx: the retail-store migration example link.
  • ai/tools/skills.mdx: the install command is now npx skills add prisma/prisma/skills.

All target paths (examples/, packages/3-extensions/, skills/) were verified to exist in the new repo, since the git history moved intact. Blog posts and changelog entries also link to the old repo but are left as historical content; happy to sweep those in a follow-up if we want.

Companion PRs from the same migration: prisma/prisma#29837 (skills-contrib) and prisma/ignite#179 (skill mirror).

🤖 Generated with Claude Code

Summary by CodeRabbit

  • Documentation
    • Updated installation instructions to use the current Prisma skills bundle.
    • Refreshed extension catalog links and repository references for pgvector, PostGIS, ParadeDB, Supabase, and arktype-json.
    • Updated Prisma Next documentation links, migration examples, and fixture setup commands to reference the Prisma repository.
    • Improved spacing and formatting around extension example guidance.

The Prisma Next codebase moved from prisma/prisma-next to prisma/prisma
as its canonical repository, so the old GitHub links are dead. Update
the clone instructions in the migration-graph page (including the cd
directory name), the extension package and example links, the source
link on the Prisma Next index page, the retail-store migration example
link, and the skills add command in the AI skills page.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@vercel

vercel Bot commented Jul 29, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
blog Ready Ready Preview, Comment Jul 29, 2026 9:45am
docs Ready Ready Preview, Comment Jul 29, 2026 9:45am
eclipse Ready Ready Preview, Comment Jul 29, 2026 9:45am
site Ready Ready Preview, Comment Jul 29, 2026 9:45am

Request Review

@coderabbitai

coderabbitai Bot commented Jul 29, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

Walkthrough

Documentation links, the AI skills installation path, and migration fixture commands are updated from prisma-next repository locations to corresponding prisma repository locations.

Changes

Repository link updates

Layer / File(s) Summary
AI and extension links
apps/docs/content/docs/ai/tools/skills.mdx, apps/docs/content/docs/orm/next/extensions/using-extensions.mdx
The skills installation command and listed extension links now target the prisma repository; nearby documentation spacing is reflowed.
Next documentation and fixtures
apps/docs/content/docs/orm/next/index.mdx, apps/docs/content/docs/orm/next/migrations/*.mdx
Repository links and the migration fixture clone command now target prisma.

Estimated code review effort: 1 (Trivial) | ~3 minutes

Suggested reviewers: sorenbs

🚥 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 clearly summarizes the main change: updating Prisma Next documentation links to point to the canonical prisma/prisma repository.
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.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch docs/point-links-at-prisma-prisma

Comment @coderabbitai help to get the list of available commands.

@github-actions

Copy link
Copy Markdown
Contributor

🍈 Lychee Link Check Report

55 links: ✅ 29 OK | 🚫 0 errors | 🔀 5 redirects | 👻 26 excluded

✅ All links are working!


Full Statistics Table
Status Count
✅ Successful 29
🔀 Redirected 5
👻 Excluded 26
🚫 Errors 0
⛔ Unsupported 0
⏳ Timeouts 0
❓ Unknown 0

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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/next/migrations/the-migration-graph.mdx`:
- Around line 118-119: Update the adjacent prose to use the canonical “Prisma
repository” naming: in
apps/docs/content/docs/orm/next/migrations/the-migration-graph.mdx lines
118-119, replace “Prisma Next repo ships…”; in
apps/docs/content/docs/orm/next/migrations/editing-a-migration.mdx line 198,
replace “Prisma Next repo's” with “Prisma repository's” or equivalent.
🪄 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: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: 9e3a7837-07bd-44e5-a89e-f6db26669312

📥 Commits

Reviewing files that changed from the base of the PR and between 002cbf6 and 00c1c9a.

📒 Files selected for processing (5)
  • apps/docs/content/docs/ai/tools/skills.mdx
  • apps/docs/content/docs/orm/next/extensions/using-extensions.mdx
  • apps/docs/content/docs/orm/next/index.mdx
  • apps/docs/content/docs/orm/next/migrations/editing-a-migration.mdx
  • apps/docs/content/docs/orm/next/migrations/the-migration-graph.mdx

Comment on lines +118 to +119
git clone https://github.com/prisma/prisma
cd prisma && pnpm install && pnpm -w build && pnpm install

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win

Use the canonical repository name in adjacent prose.

The changed links and clone command now target prisma/prisma, but nearby text still calls it the “Prisma Next repo.”

  • apps/docs/content/docs/orm/next/migrations/the-migration-graph.mdx#L118-L119: update the preceding “Prisma Next repo ships…” wording.
  • apps/docs/content/docs/orm/next/migrations/editing-a-migration.mdx#L198-L198: change “Prisma Next repo's” to “Prisma repository's” or equivalent.
📍 Affects 2 files
  • apps/docs/content/docs/orm/next/migrations/the-migration-graph.mdx#L118-L119 (this comment)
  • apps/docs/content/docs/orm/next/migrations/editing-a-migration.mdx#L198-L198
🤖 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/orm/next/migrations/the-migration-graph.mdx` around
lines 118 - 119, Update the adjacent prose to use the canonical “Prisma
repository” naming: in
apps/docs/content/docs/orm/next/migrations/the-migration-graph.mdx lines
118-119, replace “Prisma Next repo ships…”; in
apps/docs/content/docs/orm/next/migrations/editing-a-migration.mdx line 198,
replace “Prisma Next repo's” with “Prisma repository's” or equivalent.

@argos-ci

argos-ci Bot commented Jul 29, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Argos notifications ↗︎

Build Status Details Updated (UTC)
default (Inspect) ✅ No changes detected - Jul 29, 2026, 9:53 AM

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