Skip to content

chore(docs): update more 404s#7571

Open
mhartington wants to merge 3 commits intomainfrom
404-updates
Open

chore(docs): update more 404s#7571
mhartington wants to merge 3 commits intomainfrom
404-updates

Conversation

@mhartington
Copy link
Member

@mhartington mhartington commented Feb 27, 2026

Summary by CodeRabbit

  • Documentation
    • Significantly expanded the documentation redirect mappings to ensure comprehensive coverage of all legacy documentation paths and URLs. Users accessing older or bookmarked documentation links will now be automatically redirected to their current locations, improving overall accessibility and preventing broken link errors when referencing archived documentation from previous versions or external sources.

@vercel
Copy link

vercel bot commented Feb 27, 2026

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

Project Deployment Actions Updated (UTC)
blog Ready Ready Preview, Comment Feb 27, 2026 7:30pm
docs Ready Ready Preview, Comment Feb 27, 2026 7:30pm
eclipse Ready Ready Preview, Comment Feb 27, 2026 7:30pm

Request Review

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Feb 27, 2026

Important

Review skipped

Review was skipped as selected files did not have any reviewable changes.

💤 Files selected but had no reviewable changes (1)
  • apps/docs/vercel.json

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review

Walkthrough

A Vercel configuration file was updated to add approximately 123 lines of new redirect mappings in the redirects array, each routing legacy documentation paths to their new destinations with permanent status enabled.

Changes

Cohort / File(s) Summary
Redirect Configuration
apps/docs/vercel.json
Significantly expanded the redirects array with numerous new redirect mappings from old documentation paths to new paths, each marked as permanent redirects.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Why this estimate: While the changes follow a highly homogeneous pattern—repetitive redirect object structures with consistent source, destination, and permanent fields—the sheer volume of 123 added lines necessitates careful verification. The reviewer should validate that each old-to-new path mapping is semantically correct, that destination URLs are valid and properly formatted, and that no conflicting or overlapping redirect rules exist that could cause unintended routing behavior. The repetitive nature simplifies the review compared to logic-heavy changes, but the scale and semantic correctness requirements push this into moderate territory.

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title 'chore(docs): update more 404s' directly and accurately describes the main change: expanding redirect mappings in the docs configuration to handle more 404 errors.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ 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.

❤️ Share

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

@argos-ci
Copy link

argos-ci bot commented Feb 27, 2026

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

Build Status Details Updated (UTC)
default (Inspect) ⚠️ Changes detected (Review) 1 removed Feb 27, 2026, 7:36 PM

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 1

🧹 Nitpick comments (1)
apps/docs/vercel.json (1)

5614-5617: Avoid redirect chains by targeting terminal destinations.

Line 5615 and Line 5617 currently redirect to /docs/getting-started, Line 5624 redirects to /docs/reference, and Line 5669 redirects to /docs/data-platform—all of which are already redirect sources in this file. Pointing these directly at their final destinations will avoid extra 308 hops.

Also applies to: 5624-5624, 5669-5669

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@apps/docs/vercel.json` around lines 5614 - 5617, The redirects listed use
intermediate pages causing redirect chains; update each rule to point directly
to the terminal destination instead of `/docs/getting-started`,
`/docs/reference` or `/docs/data-platform`. Specifically, change the destination
for the source "/docs/reference/api-reference/prisma-schema-reference/enum" to
its final canonical page, change
"/docs/getting-started/setup-prisma/add-to-existing-project/relational-databases-node-postgresql"
and "/docs/getting-started/setup-prisma/add-to-existing-project" to their final
onboarding pages, and also fix the other entries referenced (the sources at the
locations noted that currently point to `/docs/reference` and
`/docs/data-platform`) so none of these sources redirect to another redirect
source; replace each destination with the ultimate target URL.
🤖 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/docs/vercel.json`:
- Line 5656: The redirect entry {"source": "/docs/pulse", "destination":
"/docs/pulse", "permanent": true} creates an infinite self-redirect; fix it by
either removing this rule or changing the "destination" to the intended target
(any path different from "/docs/pulse", e.g., "/docs/pulse/" or the correct
section like "/docs/pulse/overview"), and ensure no other redirect maps the same
source to itself so source !== destination for the redirect entry.

---

Nitpick comments:
In `@apps/docs/vercel.json`:
- Around line 5614-5617: The redirects listed use intermediate pages causing
redirect chains; update each rule to point directly to the terminal destination
instead of `/docs/getting-started`, `/docs/reference` or `/docs/data-platform`.
Specifically, change the destination for the source
"/docs/reference/api-reference/prisma-schema-reference/enum" to its final
canonical page, change
"/docs/getting-started/setup-prisma/add-to-existing-project/relational-databases-node-postgresql"
and "/docs/getting-started/setup-prisma/add-to-existing-project" to their final
onboarding pages, and also fix the other entries referenced (the sources at the
locations noted that currently point to `/docs/reference` and
`/docs/data-platform`) so none of these sources redirect to another redirect
source; replace each destination with the ultimate target URL.

ℹ️ Review info

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 897ec31 and 64db103.

📒 Files selected for processing (1)
  • apps/docs/vercel.json

coderabbitai[bot]
coderabbitai bot previously approved these changes Feb 27, 2026
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.

2 participants