Configuring Email Notifications for Workflow Runs

[muhammad-shameem]

I would like to Customize my workflow so that my entire team can receive or a custom email (DL) can receive a notification like whether the workflow has completed successfully or not ! As of now the one who is running the workflow is receiving the notification and there's no verified github actions here as well. for more - https://github.community/t/github-actions-email-notifications-for-workflow-failures/176028/2

[daltonv]

+1 for this issue. I have a few scheduled workflows that the whole team should be email about if they fail. Currently only the creator of the workflow gets emailed as specified here -> https://docs.github.com/en/enterprise-cloud@latest/actions/monitoring-and-troubleshooting-workflows/notifications-for-workflow-runs

[GMNGeoffrey]

Could we get a response from the team here? It is absolutely wild to me that there's no way to properly notify people when a workflow fails. That's one of the most basic features of a CI system.

[gcallah]

Yes, there should be a simple on-failure: section that can take an email step with a list of recipients.

[woodda]

Yes, AND it should use the existing hosted GitHub mail server to send those emails, just as it does with all other automatic GitHub notifications. The key is that it needs to be DYNAMIC so that the github.actor or github.triggering_actor who actually ran the GH action is listed in the FROM field of the email.

[LKreutzer]

I don't know about email but there is the rtCamp/action-slack-notify which can send you notifications to slack channels.

[LKreutzer]

This seems to be a solution: https://github.com/dawidd6/action-send-mail

[GMNGeoffrey]

This seems to be a solution: https://github.com/dawidd6/action-send-mail

Yeah I found that one. It requires providing credentials from a Gmail account. To do that properly for a team software project, it means creating your own bot email account, managing its login info, creating app credentials for it, etc. This is a really basic feature that should really be something that's built in to GitHub

[gcallah]

Plus the author doesn't support the tool, and it no longer seems to work properly.

[flodolo]

I was going to file a similar issue, but found this one. I don't think having an action should be required, this should be part of the workflow definition. An action would require an external SMTP with credentials, without forgetting that some organizations only allow vetted actions for security reasons.

From this page, for scheduled jobs:

Notifications for scheduled workflows are sent to the user who initially created the workflow. If a different user updates the cron syntax in the workflow file, subsequent notifications will be sent to that user instead. If a scheduled workflow is disabled and then re-enabled, notifications will be sent to the user who re-enabled the workflow rather than the user who last modified the cron syntax

That is not very flexible. It should be possible to specify in the workflow who should receive notifications for failures, by providing usernames or group aliases. Example:

on:
  schedule:
    # * is a special character in YAML so you have to quote this string
    - cron:  '30 5,17 * * *'
    - notify:
      - @SOMEUSER
      - @SOMEALIAS

Or it could be defined at root level, same as name, on, etc. to send notifications for every run.

[kuttyTechi]

• notify:
  - @someuser
  - @SomeAlias

Did n't worked for me, any onetried?

[flodolo]

That's a suggestion, not something they implemented.

[kuttyTechi]

Since this is basic stuff needed, i don't see any enterprise approved action for it.

[torokati44]

+1 on this.
It could even be a simple boolean in the workflow YML that switches "notify the entire organization about this workflow [instead of just the user that happened to author the last commit when the scheduled run started]".
This could then either be done by sending individual emails to every org member, or assuming that the organization email address is a mailing list, as I assume it commonly is.

[jamesrhymes]

+1, this is basic stuff

[biotia-editbalogh]

+1, this should be the baseline for notifications.

[LeoGerman]

+1

[sviswarthh01]

+1

[joergfunger]

Would like to get that feature as well

[BGMP]

This would be much appreciated indeed. I use GitHub workflows quite often, and being able to configure who gets notified and when would be really useful!

[HenryDelBosque]

+1

[samimia-swks]

+1

[kuttyTechi]

Waiting for this, please share if you guys have achieved this using any different approach

[HananBarmats]

for now - our approach was to add a comment on the failing commit with
FYI: @username
using this action:
https://github.com/marketplace/actions/commit-comment
at least until something like the requested feature is implemented.

[k-doering-NOAA]

+1. With the default settings, often those who want to know about actions failing are not notified!

[BS-jiriceska]

+1

[BartNSTCL]

+1

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

[nebuk89]

Thank you for all engaging with this and sorry I haven't caught this one when folks have commented before.

This is valid feedback and something we will absolutely consider. I don't have timelines when we 'will do this' but I have tagged as backlog so I and the rest of the Actions PMs can keep an eye on it :)

Thank you for all engaging and continuing to share with us. ❤️

[wfhoehn]

+1

[Dave-WestNeu]

+1

[Pier-areas]

Very basic stuff asked here if you'd ask me, please !

[alexanderbailey]

+1

[PsiKai]

I'm leaving an organization where I've configured many cron schedule workflows. Right now, I'm the maintainer as well, so it makes sense that I get the email on failure. When I leave, these workflows will just silently fail with no notification system.

Please Github, just a basic feature to configure a mailing list for actions failures!

[EKoczur]

If you're last commiter to those crons, they won't even trigger. You may want to review this thread: https://github.com/orgs/community/discussions/109354

[ia-mfriegang]

+1

[marko-plantic]

+1

[viccoGO]

+1

[AbdulazizBahmeed]

+1

[ascopes]

+1