Bitbucket Cloud: Getting UUID from API #964
Merged
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
…_UUID to DANGER_BITBUCKETCLOUD_OAUTH_KEY OR DANGER_BITBUCKETCLOUD_USERNAME
|
Oh great! This looks like I'd expect - thanks @HelloCore :D |
|
Thanks for the PR @HelloCore. This PR has been shipped in v9.2.9 - CHANGELOG. |
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.
From this issue, #856.
I think it's because it's difficult to get correct
UUIDfromBitbucket Cloud, so having Danger CI get it could be better.However, we need extra permission (Read Account) to get the UUID.
I think we should not recommend UUID because it's easy to make a mistake (which I've done twice), so I've removed anything related to UUID from the document.