seanaty Atlassian Team

Correct. This feature is only available on Bitbucket Server.

What is your reason for adding an SSH to a workspace? SSH keys are only meant to be added for users. The closest thing to what I think you're looking for is called Access Keys. You can upload SSH keys for each individual repository to enable `git clone` and `git pull` (read only) access only. This is useful for running…

Unfortunately there is no way to customize this. IMO there should be a project filter on the list of repositories for a given workspace. This page includes the repository descriptions. https://bitbucket.org/{workspace}/workspace/repositories

Do you have a screenshot or more details?

To add an item there you would need to create a Bitbucket Connect App. This location in particular is a WebItem at the location org.bitbucket.pullrequest.summary.actions. With this WebItem you can open up a new page or open up a dialog box whose contents are an iframe. Learn more…

Anything that can authenticate can use the reports API go create reports. While this doesn't have to be done inside of a pipeline it makes the most amount of sense to do so. I believe authenticating to this API within a Pipeline will "just work". Furthermore, it also makes sense that you'll be wanting to run a report…

You're not missing anything. You can't specify filenames as conditions for this web. Empty iframe won't work either because the title will still always show up.

Both of these APIs should require the same level of permission. 403 is the response that you'd get if passed in no authorization whatsoever (for a private repository). It is indeed odd that one of them would 200 while the other returns 403. I would check script for any typos.

Since this came up in another thread, I'm posting the public issue here: https://jira.atlassian.com/browse/BCLOUD-20811 Voting/watching this issue there will increase the chances this gets worked on.

Here is the public bug for this issue. https://jira.atlassian.com/browse/BCLOUD-20811 please upvote it there as it does help in determining priorities.

Thanks for the comment. There's a bit of an explanation here: https://community.atlassian.com/t5/Jira-questions/UUID-in-link-to-pull-request-instead-of-repository-name/qaq-p/1111287 but suffice to say you're not the only person who wishes it had something more human readable.

All build statuses are ultimately created buy calling this API https://developer.atlassian.com/bitbucket/api/2/reference/resource/repositories/%7Bworkspace%7D/%7Brepo_slug%7D/commit/%7Bcommit%7D/statuses/build Depending on what integration you're using, they'll ask for some type of credentials to be able to fetch your code…

Hi @Yak Hawkes For commit statuses to show on the pull request page the following criteria needs to be met: * the commit has of the commit status matches the current commit has of the source PR branch * if the commit status refname is null or it matches the branch name of the source branch. Double check that the refname…

Good catch about the documentation. I'll make a task to update the example. The parameter name is "workspace" but it used to actually be "username" of of the team, hence the example currently says "my-username".

Thanks again for the transparency!

Ah ok, this then is an authentication issue. When you look at your list of repos and see "0" that means you have private repositories (and no public repositories). As you are not authenticated correctly you see what the public and/or unauthenticated users see. Namely a list of your public repositories (which, in this case,…

I suspect this is not implemented and you'd have to parse the markdown for images and fetch them that way.

Based on the findings here: https://community.atlassian.com/t5/Bitbucket-questions/Re-Re-how-to-create-bitbucket-pull-request-using-bitbuc/qaq-p/912414/comment-id/33847#M33847 you can't actually add the authenticated users as a reviewer (check and see if you're doing that). Lastly I would use UUID instead of username as…

Thanks for sharing this. I really appreciate the transparency!

@izalcomax The commits API is a little bit special and not filterable using `q=`. That said there are a few handy URL params for include/excluding commits. Compare these https://api.bitbucket.org/2.0/repositories/atlassian/bbql/commits/master?fields=values.hash,values.message…

Nicely done. I've submitted and update to the docs and it should be deployed soon-ish.

Access denied. You must have write or admin access. This is also the default when you request a private repository anonymously. Something is still misconfigured with how you're making the request it seems. The scopes for your application are correct.

Because accounts can have public repositories the response here can be confusing. This tells me that authentication is failing. You're only seeing the workspace's public repositories, which is, nothing :). To troubleshoot authentication you can try fetching an individual repository that is private. As per why…

Please post the error.

No. The only customization you can do is the repo avatar.

There is this API to GET all pull requests within a repository. https://developer.atlassian.com/bitbucket/api/2/reference/resource/repositories/%7Bworkspace%7D/%7Brepo_slug%7D/pullrequests By default, it only shows open pull requests so you don't have to do any filtering, however, if you wanted to, here are some…

Unfortunately only a few API endpoints are available for use by the pipelines proxy. I don't actually have a comprehensive list but I do know that the proxy supports at least the reports API and `git push` Other than that there should be nothing special about using the Bitbucket API inside of a pipeline (versus using the…

It looks like the branch name was added to the message column. Best work around would be to enlarge the viewport or minimize the left sidebar. But I do agree that the whole row could be re-arranged to prioritize the commit message and that, I think is the most important column in this table.

@StuMid the code search API only indexes the main branch so you're correct that you can only use this API with that branch to search file contents. That said, you can use the src API to fetch files from any branch given that you know the filename.…

Yes it's possible. If you have write access, you'll see an "edit" button for each file. You can then make changes and click "commit" which will also give an option to open a pull request. You can also add a new file by selecting "Add file" from the "..." menu in the file section.