-
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
Trigger time based escalations #68
Conversation
bad8439
to
903a140
Compare
371636c
to
6bddc85
Compare
903a140
to
b5bcddf
Compare
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.
First few comments only, i.e. those until I noticed that I should probably look at #67 first.
b5bcddf
to
8e29178
Compare
8e29178
to
fcfb235
Compare
72f0f89
to
c48835b
Compare
9150312
to
fcfb235
Compare
fcfb235
to
bee18d4
Compare
3d14c51
to
f44c4b6
Compare
bee18d4
to
f2cb44c
Compare
f2cb44c
to
f62d32b
Compare
115a60a
to
24b6dd0
Compare
f62d32b
to
14f0014
Compare
a08d873
to
28ad757
Compare
28ad757
to
d127963
Compare
d127963
to
1b8b219
Compare
Co-Authored-By: Julian Brost <[email protected]>
1b8b219
to
bc6536e
Compare
Co-authored-by: Yonas Habteab <[email protected]>
bc6536e
to
bbb9edc
Compare
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.
One message in the event is incorrect. Apart from that, this PR should be good to go.
b8f9924
to
e45cc3e
Compare
Otherwise, the notification subject is looking odd, since this field is used to build the notification messages.
e45cc3e
to
f45fe6f
Compare
fixes #63