-
Notifications
You must be signed in to change notification settings - Fork 0
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(ci): notify via slack when a publishing workflow fails #525
Conversation
|
fixes #409 |
fixes #409 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Lets us fix errors and merge it
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Much better! thank you 💯
* chore(ci): uses shared notification if workflow job fails * chore(ci): adds pr for testing * chore(ci): changes to fully qualified url * chore(ci): makes use of the shared workflow correctly * chore(ci): passes webhook as input * chore(ci): reads webhook from input * chore(ci): passes the webhook as secret * chore(ci): adds mapping * chore(ci): sets secrets not within with statement * chore(ci): adds valid json * chore(ci): formats the body * chore(ci): formats the title * chore(ci): removes double JUNO on title * chore(ci): sets body rich per var * chore(ci): sets inline envs * chore(ci): sets playload in a new step * chore(ci): corrects envs json syntax * chore(ci): ensures the JSON output is compact and valid * chore(ci): adds tests with rich body * chore(ci): cleans up the call * chore(ci): adds branch to the shared task * chore(ci): removes test * chore(ci): tests reuse action in release * chore(ci): removes double quotes * chore(ci): adds test * chore(ci): adds test integration * chore(ci): adds last test * chore(ci): removes tests and setups release * chore(ci): fixes copy paste errors --------- Co-authored-by: Andreas Pfau <[email protected]>
Summary
To ensure we're notified of any publishing failures, integrate Slack into the workflows so that a notification is posted whenever the workflow fails. This is crucial because workflows that react to a push on the main branch run after the PR is merged. At that point, there is no active control by the developer, and if the developer isn't self-checking the action logs, any issues that arise could go unnoticed. With Slack notifications, we can proactively alert the team of any failures, ensuring that problems are addressed immediately.
Changes Made
Related Issues
Screenshots (if applicable)
Testing Instructions
npm i
npm run TASK
Checklist