-
Notifications
You must be signed in to change notification settings - Fork 52
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
Notify on CI failure #161
Comments
I currently get email notifications when the staging tests fail, but I might be the only one (I wonder if it picked me because I committed the workflow?) I'll look into some email and other notification actions, and see if there's anything that more generally fits the bill. |
I did some looking around, and it seems like Slack has an official GitHub Action here: https://github.com/slackapi/slack-github-action It supports a few different authentication methods, at least two of which (Slack Apps, incoming webhooks) should work with the current Sigstore slack (which is on the free plan). |
I've also used https://github.com/peter-evans/create-issue-from-file in the past which works well |
That looks nice! Keeping things on GitHub's side will also save us quite a bit of complexity/token management. I can move forwards with that. |
Description
We have some tests that run on a schedule to ensure the client continues to work against Sigstore's staging instance, but we have no way to be notified if they start failing, and we'll likely move these to only run on main/cron and not on PRs (ref: #159).
We should have some way to notify maintainers when these jobs start failing, perhaps by automatically opening an issue on this repository, or email notifications.
The text was updated successfully, but these errors were encountered: