Skip to content

Batch fix 404s#17522

Open
coolguyzone wants to merge 2 commits intomasterfrom
coolguyzone/chore/mass-404-fix
Open

Batch fix 404s#17522
coolguyzone wants to merge 2 commits intomasterfrom
coolguyzone/chore/mass-404-fix

Conversation

@coolguyzone
Copy link
Copy Markdown
Contributor

@coolguyzone coolguyzone commented Apr 28, 2026

DESCRIBE YOUR PR

Created this PR using Claude, but I've manually tested all the redirects.

IS YOUR CHANGE URGENT?

Help us prioritize incoming PRs by letting us know when the change needs to go live.

  • Urgent deadline (GA date, etc.):
  • Other deadline:
  • None: Not urgent, can wait up to 1 week+

SLA

  • Teamwork makes the dream work, so please add a reviewer to your PRs.
  • Please give the docs team up to 1 week to review your PR unless you've added an urgent due date to it.
    Thanks in advance for your help!

PRE-MERGE CHECKLIST

Make sure you've checked the following before merging your changes:

  • Checked Vercel preview for correctness, including links
  • PR was reviewed and approved by any necessary SMEs (subject matter experts)
  • PR was reviewed and approved by a member of the Sentry docs team

LEGAL BOILERPLATE

Look, I get it. The entity doing business as "Sentry" was incorporated in the State of Delaware in 2015 as Functional Software, Inc. and is gonna need some rights from me in order to utilize my contributions in this here PR. So here's the deal: I retain all rights, title and interest in and to my contributions, and by keeping this boilerplate intact I confirm that Sentry can use, modify, copy, and redistribute my contributions, under Sentry's choice of terms.

EXTRA RESOURCES

@vercel
Copy link
Copy Markdown

vercel Bot commented Apr 28, 2026

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

Project Deployment Actions Updated (UTC)
develop-docs Ready Ready Preview, Comment Apr 28, 2026 10:45pm
sentry-docs Ready Ready Preview, Comment Apr 28, 2026 10:45pm

Request Review

Copy link
Copy Markdown
Member

@sergical sergical left a comment

Choose a reason for hiding this comment

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

should we invest some resources looking into where these URLs are coming from and why they exist? Do we have telemetry setup on 404 hits and how we can prevent these from growing in the future?

cause this isn't part of the lint 404s github action we have since these urls werent actually hardcoded in the docs content that link out to 404s, these are coming from external sources, right?

also did any of these get picked up by open 404 issues or was that what claude worked on here? 👀

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