-
Notifications
You must be signed in to change notification settings - Fork 245
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Comment for Bitbucket stopped working #346
Comments
This bug could be closed after this pull request #352 is merged. |
Is there any prediction on when the version with bitbucket API v2 support will be released? |
The PR has been merged. I would like to get a few others merged in before cutting a new release. Is it possible for you to point to GH for now? |
Unfortunately not. |
@doomspork I pointed the pronto gem to use the master branch and there still appears to be error around comments. Now though it's an error with #parse_comments. I'm very unfamiliar with the bitbucket api, but I'm wondering if how the responses are parsed needs to get updated as well. |
See this PR, it should fix it #354 I had issues too |
Apparently pronto still uses bitbucket v1.0 API for reading and posting comments. This API has just been removed (it now returns http error code 410).
We need to update to v2.0 API to keep this behaviour.
The text was updated successfully, but these errors were encountered: