Dan Fraser Atlassian Team

Comments

  • Hi @Nikolai Marov Thanks for your feedback, sorry it's taken so long for us to reply, today is my first day back for 2024. Let me address both points individually, as I believe their independent feature requests. Validate commit message when user clicks merge second time in Dialog I think exposing the submitted commit…
  • Hi @Mykhailo Pavliuk Thanks for reaching out, what you're seeing is actually the intended behaviour. I think you've highlighted that we need to improve the Repository Settings page to explicitly call out that unless you install (and develop) a Forge app which contains a bitbucket:mergeCheck module, there will be no checks…
  • Hey @M H , Thanks for reaching out. You're correct in your interpretation of the OAuth specifications, that is a secret is not needed for public OAuth consumers. However, I believe the reason they've stated that requiring a secret for a public consumers is `NOT RECOMMENDED` is due to the fact that it's called a secret yet…
  • Hi @Evelin Szabados, Welcome to the Atlassian Community and thanks for your question. As you've worked out, there is currently no webhook, or other mechanism, to be notified of the revocation of an OAuth consumer. I'd suggest raising an issue (of type Suggestion) under the public BCLOUD project…
  • Hi @Indu Devanath, I've pushed a change which should fix this for you. Could you please try again and confirm that you're able to retrieve the file via the API? Best regards, @Dan Fraser 
  • Hey @Marat Bakeev, From what we can see of the curl traces you provided, your PC appears to return an incorrect IP address when doing the DNS lookup of `api.bitbucket.org`. You'll notice in your trace it shows this line `* Trying 104.192.141.1:443...` Authoritative nameservers for bitbucket.org will return 18.205.93.8,6,7…
  • @M H , instead of raising a bug, I've done you one better. I've patched the code to allow the port to be specified at runtime on 127.0.0.1 and the functionality should be available now in production. Note that the existing behaviour still works for localhost, as we have to continue supporting this. We have many consumers…
  • Hi @M H Thanks for your question, and welcome to the Atlassian Community! I can confirm that Bitbucket's OAuth2.0 implementation does allow the port to be specified at request time (only for localhost). When setting up your OAuth Consumer, you'll need to specify your Callback URL as http://localhost. Note that you can have…
  • Hi @bdbowen I'm a dev on the team which owns the bbql library. I've patched the issue this week, could you please confirm it's fixed your problem? Edit: Sorry, we've had to hold off on the rollout of this. I'll continue to look into this next week. Edit: The changes are live as of 3:00pm Sydney time 15th July. Feel free to…