Skip to content
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.

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

chore(slack): correctly type issue message builder #74876

Merged
merged 10 commits into from
Jul 29, 2024

return new option group type

e8f5bc1
Select commit
Loading
Failed to load commit list.
Merged

chore(slack): correctly type issue message builder #74876

return new option group type
e8f5bc1
Select commit
Loading
Failed to load commit list.
getsantry / getsentry / frontend skipped Jul 26, 2024 in 13s

Tests skipped (no frontend files changed)

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/74876

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