Updated Bitbucket backends to use newer v2.0 APIs#652
Merged
omab merged 2 commits intoomab:masterfrom Jul 9, 2015
Merged
Conversation
Contributor
Author
|
Following up, can someone take a look at this? |
omab
added a commit
that referenced
this pull request
Jul 9, 2015
Owner
|
Changes merged with the small change to keep some degree of backward compatibility with the username-as-id behavior. Thanks |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Bitbucket has had a v2.0 version of their REST API out for some time. This PR updates the Bitbucket backend to use the v2.0 REST API for user and e-mail resources.
In addition, this PR follows the Bitbucket API documentation guidance that user UUIDs should be used as account identifiers instead of the username since usernames can change.