-
Notifications
You must be signed in to change notification settings - Fork 244
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
failed to create an incident #165
Comments
Looks like a bug in the implementation of
This is a bit different than other implementations, for example consider
The difference is that with I'll open a PR with the fix shortly. |
I saw your fix. It would be really helpful for me if this gets merged. Is there any workaround till that? |
@snaveen My PR being merged is up to the maintainers of PagerDuty/go-pagerduty If you want to use my fork for the time being I've gone and merged my fix into master there: https://github.com/joepurdy/go-pagerduty I'll do my best to keep the fork updated with upstream, but ultimately the best fix would be the maintainers merging the fix into upstream. |
Thanks @joepurdy |
I think I have merge access, let me see if I can do the needful tonight (Pacific time). |
@theckman could you help us on this? |
@ranjib Could you help us on this? |
Here is my code:
I have the title correctly set.
But I got the error like:
Does anyone know what is wrong?
The text was updated successfully, but these errors were encountered: