docs(seer): The Seer specific github integration is deprecated. Use the Sentry one for full support

[ryan953]

DESCRIBE YOUR PR

The Seer integration is deprecated.
When it was created it asked for all the permissions needed for autofix to work, reading the repo and whatever else was on the list. This was to enable the v1 Issue Scan & Issue Fix workflow. what we now call 'legacy seer'.

Recently the Sentry integration has been updated to ask for the same permissions. Also, the Sentry integration is the one that code-review runs through. So for fully Seer support people should switch over to the Sentry integration.

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: March 15
• 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

EXTRA RESOURCES

• Sentry Docs contributor guide

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
sentry-docs	Ready	Preview, Comment	Mar 11, 2026 5:32pm

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
develop-docs	Ignored	Preview	Mar 11, 2026 5:32pm

[bruno-garcia]

Should we mention that a permission has been requested?
"If you installed the Sentry GitHub app before date X, note there might be new permissions requested" ?

Maybe I'm overthinking

[ryan953]

Should we mention that a permission has been requested? "If you installed the Sentry GitHub app before date X, note there might be new permissions requested" ?

Maybe I'm overthinking

Lets do that in another PR where we just talk about the Sentry integration.

I have https://github.com/getsentry/sentry-docs/pull/16835/changes started, i'll put it in there and avoid merge conflicts.

[sfanahata]

Not blocking, but I think this would look better as an alert. Added the suggested change in a comment.