-
Notifications
You must be signed in to change notification settings - Fork 302
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
Fix suggestion for #960 #1061
Fix suggestion for #960 #1061
Conversation
Seems like some checks are failing due to the scripts that are not changed by this PR:
|
Hi,
|
Hi @Nowheresly, Thanks for directly pointing out to the root cause. I updated the test cases and all the checks have passed successfully. |
Hi @Nowheresly, Please let me know whether the PR is eligible to merge. |
Yes, it seems good to me. |
Thanks for your contribution. |
Hello,
I simply added " - triggered" or " - resolved" to the end of e-mail's subject regarding the status. Similar feature is already implemented for PagerDuty and Slack alerts.
Although it is not configurable, it would address the requirements listed #960.
Note: I work in an enterprise environment and it is nearly impossible to retrive artifacts and compile the project. (Enterprise Maven repo setting, proxy setting, proxy certificate problems, SSL handshake problems, node-14.21.X-win-x64.zip package downloading problems, missing node.exe execution grants in Maven target directory, conflict with the node installation on the machine etc.) Because, I was only able to compile Java modules -by skipping tests- and failed to compile ui part, there could be other dependencies which I could not aware of.
Regards,
Ali Sadik Kumlali