Bitbucket deprecated its API v1.0: update all endpoints to API v2.0 #352
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
added 10 commits
July 1, 2019 13:49
(pull_requests wasn't updated)
|
@starchow sorry for the delays 🎉 |
apiology
pushed a commit
to apiology/pronto
that referenced
this pull request
Dec 27, 2019
…rontolabs#352) * Bitbucket deprecated its API v1.0: update all endpoints to API v2.0 (pull_requests wasn't updated) * Fix issue of approve_pull_request and unapprove_pull_request method * Fix github create pullrequest comment issue * Fix bitbucket create pullrequest comment issue * Update bitbucket API v2 pullrequest format * Update bitbucket API v2 pullrequest format * Rollback bitbucket.rb and parse new bitbucket comment format * Rename position to line_to * Fix duplicate pullrequest comment
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
After 2 pull requests #347 and #348 it still not working correctly. I submit this pull request to fix it completely.
@doomspork please take a look, thanks