Caroline R Atlassian Team

Hi, Henrique, thanks for the additional information. I confirmed that even though you are the only admin of this workspace, you did not have access to the group that has access to the repository. In this case, I added you to this group, so you should have received an invitation to join this group. After accepting that, you…

Hi, @asperry, yes, this is what I meant :) Kind regards, Caroline 

Hi, Ruchi, welcome to the community! I reviewed your email and confirmed that it had a block on the server that prevented emails from being sent to you. This can occur when the system tries to send an email to the user and the account does not exist, is not activated yet, or rejects the email for some internal reason. In…

Hi, Carlos! Thanks for your confirmation, I'm glad to know you can access your account now. Kind regards, Caroline 

Hi, Carlos! Welcome to the community! I confirmed that your Bitbucket account was indeed set as inactive, so I reactivated it. Could you please try to access it now and let me know how it goes? Looking forward to hearing from you. Kind regards, Caroline

Hi, @jim-frenzel, thank you for reaching out to Atlassian Community. Checking the output you have shared with us, it looks like git didn’t ask you to inform a password, is that correct? If that’s the case, git is probably using some password stored in your Windows credentials. Could you please make sure you have deleted…

Hi, @asperry, welcome to the community! As you confirmed you removed some large files from your repository history and force pushed these changes to your remote repo, I believe the remote still have some dangling commits that need to be removed with a GC. In this case, I can run a GC on the remote repo to remove any…

Hi, @HaiXin.Sun, welcome to the community! Checking the Bitbucket account linked to the email you used to create this question, I was able to confirm that it was inactive, so I reactivated it. Could you please try to access it now and let me know how it goes? Looking forward to hearing from you. Kind regards, Caroline

Hi, @Oleg Vegera. Could you please confirm if after removing these large files you have pushed the changes to your remote repository? As I have increased the repo size to more than 4 GB, you should be able to push it now. Also, can you please share the workspace/repository name masked (with asterisks) so I can confirm we…

Hi, @Maximilian F, welcome to the community! I've reproduced your scenario (a private repository in a public project) and tried to delete this repository and was able to do that, so we can confirm this is not the reason you can’t delete this repo. In order to further investigate what is happening here, could you please…

Hi, @Oleg Vegera, welcome to the community! I found a repository that you have access to that was showing 4.8 GB, so I run the GC against this repo, but the size didn’t change. In this case, I have temporarily increased the repository size, so you can push the changes to the remote (without the large files). After that,…

Hi, Karsten. Indeed, it's not possible to remove it from the "switch to" menu. In this case, I have created a feature request to Allow admins to remove the products they don't use from the "Switch to" tab: * https://jira.atlassian.com/browse/CLOUD-11422 I would suggest that you add your vote there (by selecting the Vote…

Hi, @Oleg Vegera, welcome to the community! I would like to ask if you could please create a new question for your issue, providing details on the errors you see. We generally encourage users to create a new question for their issue instead of posting on someone else's question, because 1) the root cause and resolution may…

Hi, Jason, We have created a feature request to add the ability to transfer OAuth consumers between workspaces, you can access this feature through the following link: * https://jira.atlassian.com/browse/BCLOUD-21766 I would suggest that you add your vote there (by selecting the Vote for this issue link) as the number of…

Hi, Pitch, thank you for reaching out to Atlassian Community. As we’ll need to know the public SSH key to further investigate this case, I have created an internal ticket for you using the email of your community account, so you don't have to share this information here. You should have received an email with a link to the…

Hi, @Pankaj Jangid, I tested this on my side and confirmed that this is happening because currently, the branch permission dropdown will only show 5 results. So, if you have more than 5 users/groups in this repo, you will need to type their names to be able to see them. In this case, I created a feature request to show…

Hi, @Maximilian F, welcome to the community! I ran the GC against your repository and managed to reduce its size to 53.5 MB. I also would like to share with you that we have a feature request to allow users to mark repositories for git GC, as you can check here: * https://jira.atlassian.com/browse/BCLOUD-11593 Please…

Hi, Rich, welcome to the community! I was able to find a workspace with the workspace ID you mentioned and confirmed it was created yesterday and you are the admin of this. In this case, I would like to ask you to follow the next steps and confirm if you can see it: * Open your Bitbucket account > click on your avatar >…

Hi, Abel, welcome to the community! My assumption is that the API is not returning any results when you try to run it using an OAuth linked to a shared workspace, is that correct? In case you are not familiar with shared and personal workspaces, you can read more about their differences here. In summary, the personal…

Hi, @Hugo Paulo, welcome to the community! Before we start, I would like to confirm if you are trying to run a git pull or if you want to create a Pull Request to your remote repository using an API call. If you are trying to run a git pull using an App Password, the first thing you need to confirm is if you are using the…

Hi, @Pankaj Jangid, thank you for reaching out to Atlassian Community. As this Administrator group has admin access over this repository, you should be able to add it to the branch permissions. I tested it and it’s working for me, however, I need to start typing the group name to see it in the dropdown. Could you please…

Hi, Thirukumaran, thank you for reaching out to Atlassian Community. As you confirmed you have added this group to this repository with write permission, you should be able to add it to the branch permissions as well. I tested it and it’s working for me, however, I need to start typing the group name to see it in the…

Hi, @willking101, thank you for reaching out to Atlassian Community. As we’ll need to know the workspace ID and repository name to further investigate this case, I have created an internal ticket for you using the email of your community account, so you don't have to share this information here. You should have received an…

Hi, @Mbhaskara_rao, welcome to the community! Currently, Bitbucket Cloud does not have service accounts, but we have the following feature request to have this functionality implemented. I'd advise you to add yourself as a watcher to it to receive any updates and add any comments you think are necessary and/or important to…

Hi, Conor, thanks for your confirmation. Checking our logs, I don’t see any non-delivered emails, so I would like to ask you to check your spam folder or if you have certain rules that make emails skip the inbox. Is anyone else having this problem or is it just your email? Could you please confirm when you start facing…

Hi, @Le Thanh Binh! Thanks for your confirmation :) 

Hi, @Conor Croke, welcome to the community! I confirmed your email is not blocked, so this is not the reason you are not receiving these notifications. You mentioned you have this option checked in your notification settings, could you please confirm if you are referring to the "Someone mentioning me" option in your…

Hi, @payamka, welcome to the community! By your description, it seems that the issue you are facing is related to the recent changes with the removal of support for Atlassian account password for operations GIT over HTTPS and API requests. This was announced in our Blog post Deprecating Atlassian account password for…

Hi, @[deleted]. Thanks for the additional information. Allow me to reply to each of your questions directly and feel free to share any further questions or concerns about the information we will share with you. There seem to be a number of bugs. If I have a commit message such as […] then the PR description seems to munge…

Hi, @Martin Fischer, welcome to the community! Currently, this is not possible yet as repositories are identified by workspace-id/repo-name. However, we already have the following feature requests to include the project ID to the repository URL, which would allow you to create two repositories with the same name in…