-
Notifications
You must be signed in to change notification settings - Fork 245
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
Bitbucket deprecated its API v1.0: update all endpoints to API v2.0 #354
Conversation
(pull_requests wasn't updated)
…chow-master # Conflicts: # lib/pronto/clients/bitbucket_client.rb
thanks @bradrees, let's wait @doomspork review and merge it :D |
Actually, I'm getting duplicate comments on the commit/pr, I'll try investigate the cause. It appears to be that the existing comments are not being read or matched to the new ones. |
At the moment it just gives an obtuse NoMethodError when the response does not contains a 'values' key
I've included paging to get all the comments, which addresses the duplicates issue. I've been using this for a few weeks and it appears all good now! |
All merged, it is good to go! |
@doomspork could you take a look, @bradrees fixed all conflicts. |
Currently if you create a top level 'file' comment on the PR, it breaks as the comment has no line property
Merging of 3 pull requests #347, #348 and #352, plus my changes to update the endpoints.
The only significant change here is to use the
commit
endpoint instead of the removedchangeset
endpoint. This appears to be working for me, and I'm getting the comments on my commit as per before the v2.0 change.@doomspork, @starchow please take a look, thanks!
https://developer.atlassian.com/bitbucket/api/2/reference/resource/repositories/%7Busername%7D/%7Brepo_slug%7D/commit/%7Bnode%7D/comments#post