-
-
Notifications
You must be signed in to change notification settings - Fork 368
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
[BUG] Multiple inline comments don't work #1134
Comments
Cool, yeah, maybe the API usage rules changed this since this was originally built out. I don't use inline messages, so I'm unlikely to fix it - but I'd accept PRs 👍🏻 |
Seems like the multiple inline comments have started working correctly all of a sudden, I haven't updated any dependencies so I'm guessing something might have changed serverside from GitHub? Since this has started working correctly I'm going to close this issue. |
Actually I jumped the gun on closing this. I thought this was fixed because my CI ran a few times and every time it re-ran the PR it posted one new inline comment at a time. Then when I took a look at the PR it looked like danger had posted all of the inline comments at once but in reality it only added one at a time per each CI run. So I'm re-opening this issue as it's not fixed. I'm still seeing the same error messages in my CI logs when danger tries to post multiple inline comments. |
Issue was resolved in #1176 ! Closing. |
Describe the bug
When you try to post multiple inline comments, only the first comment is posted while the others fail (but still appear in the overview comment).
To Reproduce
Steps to reproduce the behavior:
yarn danger ci
from your CIExpected behavior
Danger should post all of the inline comments requested.
** Your Environment**
Additional context
When running danger with the following command:
DEBUG={*} yarn danger ci
I see that there seem to be two requests made to the same endpoint at almost the same time (maybe related to the error?) and then we can see that the request failed with an error from the GitHub API:This seems related to danger/swift#301
The text was updated successfully, but these errors were encountered: