Skip to content

fix(seer): Update no-repo warning to error severity #111410

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
chromy wants to merge 1 commit into
base: master
Choose a base branch
from
+4 −2

fix(seer): Update no-repo warning to error severity

838948a
Select commit
Loading
Failed to load commit list.
Draft

fix(seer): Update no-repo warning to error severity #111410

fix(seer): Update no-repo warning to error severity
838948a
Select commit
Loading
Failed to load commit list.
getsantry / getsentry / backend (NOT REQUIRED - selective testing) skipped Mar 24, 2026 in 11s

No relevant tests (no relevant getsentry tests)

View the workflow run on getsentry

Running against master

Details

More information

What is this?

This is a check to make sure your Pull Request passes tests on our private getsentry repo. We use GitHub Actions to
dispatch a workflow run on getsentry which creates this Check and eventually reports back the test results.

Read the below point on what to do if this Pull Request requires changes in getsentry.

What do I do if this is failing?

First, make sure your branch on sentry is update to date with master,
as getsentry could be depending on a change that exists in master but
does not yet exist on your feature branch.

If this check is still failing, it probably means the test(s) on getsentry are broken.

You will need to open a PR on getsentry, fix the problem, and add

Requires https://github.com/getsentry/sentry/pull/111410

in the PR description (NOT a comment) to have it run against this PR.

View more details on getsantry