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

Notify on post- or non-PR failures #62

Closed
DerekRoberts opened this issue Jan 20, 2022 · 2 comments
Closed

Notify on post- or non-PR failures #62

DerekRoberts opened this issue Jan 20, 2022 · 2 comments
Labels
enhancement New feature or request

Comments

@DerekRoberts
Copy link
Member

DerekRoberts commented Jan 20, 2022

Post PR steps, like cleanup, or scan results should be brought to our attention. GH issues seem like the right choice. Also relevant for cronjobs.

Types:

  • PR close (e.g. cleanup)
  • On merge
  • Cronjobs

Read:
https://www.ravsam.in/blog/send-email-notification-when-github-action-fails/

@DerekRoberts DerekRoberts added the enhancement New feature or request label Jan 20, 2022
@DerekRoberts DerekRoberts reopened this Jan 21, 2022
@DerekRoberts DerekRoberts reopened this Jan 21, 2022
@DerekRoberts DerekRoberts self-assigned this Jan 21, 2022
@DerekRoberts DerekRoberts changed the title Create issues on triggers Notify on post- or non-PR failures Jan 21, 2022
@DerekRoberts DerekRoberts removed their assignment Jan 21, 2022
@gormless87 gormless87 added the low label Jul 5, 2022
@DerekRoberts DerekRoberts removed the low label Sep 9, 2022
@DerekRoberts
Copy link
Member Author

Action to send email. Ideas by @abschwenker.
https://github.com/abschwenker/SIMS-Fork/blob/main/.github/workflows/Send-notification.yml
pretty sure for that you can use the above + and if: alwys() and a ${{ job.status }}

@DerekRoberts
Copy link
Member Author

Email ended up being problematic. Now we can notify on a README.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Archived in project
Development

No branches or pull requests

2 participants