-
Notifications
You must be signed in to change notification settings - Fork 92
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
A few incident trigger tweaks #228
A few incident trigger tweaks #228
Conversation
Signed-off-by: John Seekins <[email protected]>
Signed-off-by: John Seekins <[email protected]>
Signed-off-by: John Seekins <[email protected]>
Signed-off-by: John Seekins <[email protected]>
Signed-off-by: John Seekins <[email protected]>
Signed-off-by: John Seekins <[email protected]>
Signed-off-by: John Seekins <[email protected]>
Signed-off-by: John Seekins <[email protected]>
Signed-off-by: John Seekins <[email protected]>
Signed-off-by: John Seekins <[email protected]>
Both these functions are working correctly for us, but I'm happy to discuss how we could go about integrating them. |
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.
I don't have access to a live PagerDuty account these days, but everything here appears solid. If you'll npm version minor
and push that up to the branch, I can get it merged. Thank you! 🚀
Unrelated, I added #229 because we need a bit more confidence that changes like this one won't inadvertently bust an existing workflow. It's been on the TODO list for a while.
pager me <schedule> <minutes>
didn't support quotes around the schedule name. This is inconsistent with every other case of schedule names. I think I fixed that up correctly.pager default trigger
and send a message to a default schedule. I believe the changes I made around 160 should facilitate that, but would love some advice on how best to make that change.