-
Notifications
You must be signed in to change notification settings - Fork 105
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
Subscribe to failed Github Actions #316
Comments
Any news on this? |
We are also very interested in this |
On the Azure Service Operator project we have a number of automatic workflows that do useful things - like ensuring our documentation is up to date, or publishing updates to our website. These workflows are pretty boring - except when they fail. We want to know that they're failing pretty promptly - and notification emails get lost in the noise of other notifications. Subscribing to those workflows so we see cards in our Teams channel is ideal - but the cards from successful runs aren't very interesting. We'd love the ability to subscribe to just failed workflows, so that we see cards when (and only when!) there's an action required on our part. |
I think that this is one of the most important issues the bot has to provide. Is there a way we can also contribute so we can provide the functionality? |
I'm also interested in this, frankly it's the only reason I got this integration and this feature doesn't exist... |
Also looking for this, I would like to probably on the workflows filter, pass that I only care about the failed builds. We were using the teams webhooks, and explored creating our own integration, but is is very close (I think) |
Is your feature request related to a problem? Please describe.
Ability to subscribe on only Github Actions with status failure. This is helpful when we want to catch only the failed deployments.
Ability to write something like:
@github subsribe owner/repo workflows{name:"workflow-name", event:"status:failure"}
Describe alternatives you've considered
Alternative is to subscribe to all production deployments, but we want to catch only the failed ones. T
Additional context
None
The text was updated successfully, but these errors were encountered: