Take the Seer review check out of your branch rules before December 8
Sentry is removing Seer Code Review on December 8, 2026. Automatic reviews and the
@sentry review
command stop on that date, while Seer Autofix stays part of Seer. Sentry's help center asks teams with Code Review in their CI process to remove it before December 8 to keep their builds running. Here we walk through the GitHub side of that cleanup, because a forgotten rule there can quietly block merges once the date passes.
The required check on GitHub
On GitHub, Seer Code Review reports a check run named Seer Code Review
from the sentry
app, and we saw it under that name on public pull requests in November 2026. Some teams add that check to a branch protection rule or a ruleset as a required check. GitHub then expects it to report on every new commit. According to GitHub's documentation, a required check has to pass on the latest commit of the pull request, and only success,
skipped
and neutral
count as passing. After December 8 Seer will have nothing left to report, so we expect any pull request that still requires the check to wait for a result that never arrives.
Step 1: find every rule that requires the check
GitHub keeps classic branch protection and rulesets in different places, so look in both. For classic branch protection on a branch such as main, this command lists the required checks:
gh api repos/OWNER/REPO/branches/main/protection/required_status_checks
You can define a ruleset on one repository or across an organization. An organization ruleset applies to every repository it targets even when the repository settings look clean. These two commands list them, and you can open each ruleset by its id to read its required status checks:
gh api repos/OWNER/REPO/rulesets
gh api orgs/ORG/rulesets
Look for Seer Code Review
in the results. Teams that manage branch protection with Terraform or a similar tool should search that code as well. Otherwise the next apply restores whatever someone changed by hand in GitHub.
Step 2: remove the required check
Remove Seer Code Review
from each rule you found, either in the repository or organization settings or in your config code. Doing it before December 8 means no pull request opened on or after that day waits on the check. When the check is informational rather than required, nothing will block, though you may still have a workflow step or script that waits on it, and you can delete that too.
Step 3: switch off reviews in Seer but keep the app installed
Sentry's help center says to leave the Sentry GitHub or GitLab app installed, because Seer Autofix still needs those integrations. Switch off Code Review in your Seer settings instead. Sentry's docs also say that until December 8, enabling Code Review on a repository starts active contributor pricing, so look at your Sentry billing settings when you pick the timing.
Step 4: tell your reviewers what changes
Seer left comments when it predicted an error, and some teams read its check as a sign that someone had looked at a pull request. That signal ends with Seer. Write down in your contributing guide or team channel who reviews what from now on, and give extra thought to large pull requests written with an AI coding agent.
What to use next
Pick a replacement based on what you relied on Seer for. If you want another tool that writes review comments, compare the AI reviewers on their pricing and on how they handle your languages. Pull requests that have grown too large to read in one pass need something different. StructPR groups the files in each GitHub pull request by business area, such as authentication or database migrations, and a reviewer reads related changes together. It does not write review comments or predict production errors the way Seer did, and it works with GitHub only. You can see how it compares with Seer on our Seer Code Review alternative page, and the free plan covers one repository and 10 pull request analyses a month.
We checked these sources on November 19, 2026.