Caroline R Atlassian Team

Hi, @Akshay b! Thank you for reaching out to Atlassian Community! I was able to enable Pipelines in a repository using the API you mentioned. By the error message you shared with us, the problem seems to be in the repository. If, for example, I change the repository name for some repo that doesn’t exist, I get the same…

Hi, James! Thanks for your confirmation, I'm glad to know it worked! Kind regards, Caroline 

Hi, @James Maljaars! Welcome to the community! Thank you for reaching out to Atlassian Community! Indeed, when trying to access the link you shared with us, I receive the same error message. However, if I add a slash (/) to the URL, I can load the repository normally. Could you please test this and let me know how it goes?…

Hi, @Maxwell Cohen! Welcome to the community! Since you are using HTTPS, I suggest you try using an App Password to authenticate with git. These are substitute passwords for a user account, designed to be used for a single purpose with limited permissions. App passwords can be used to run Git commands over HTTPS to a…

Hi, @Saurabh Patwardhan. My suggestion would be that you create a separate question for your issue, providing details on the errors you see and also whether the problem occurs on Bitbucket Cloud or Bitbucket Server. We generally encourage users to create a new question for their issue instead of posting on someone else's…

Hi, @Alexandre Tolstenko! Thank you for reaching out to Atlassian Community! We definitely can help you recover this repo. However, I checked the Bitbucket account associated with the email you used to create this question and it doesn’t have access to the workspace you mentioned. If you still have access to this other…

Hi, Prabir! I'm glad to know the information was useful to you. Please feel free to share any additional questions or concerns regarding this case. Kind regards, Caroline 

Hi, Dominik! Thanks for the update, checking this account, I was able to find the repository that was over 2GB. I ran the GC and the repo size is now 427.6 MB. Please, feel free to share any additional questions or concerns regarding this case. Kind regards, Caroline 

Hi, @Akshay b! Thanks for getting back to us and confirming the API worked. I'm glad to know you were able to delete your repo! Kind regards, Caroline 

Hi, Sam! Thanks for your confirmation, I'm glad to know it worked! Kind regards, Caroline 

Hi, @Akshay b, Thanks for sharing the sentry code with us. I checked that and it corresponds to the below error: ProjectPrivacyException: A repository in a private project cannot be publicly visible. So the repository you are trying to delete is set as public, but the project that has this repository is private. This is…

Hi, @Sam Wainwright! Welcome to the community! Artifacts are not uploaded for the failed steps. Bitbucket pipelines are configured to stop at any non-zero exit code. That means that the pipeline execution is stopped when cypress fails the tests. Because artifacts are stored after the last step of the pipeline, you won’t…

Hi, @Akshay b! Thank you for reaching out to Atlassian Community! The “Something went wrong" message usually comes with a 5xx response that shows a Sentry ID code. This code may give us some indication of what is causing this issue. In this case, could you please follow the next steps to find the Sentry ID, so I can…

Hi, @Prabir Senapati! Welcome to the community! Checking the workspace you shared here, we can see that this is a personal workspace, not managed, that belongs to the user you would like to remove; they are the admin/owner of this account, so we can’t remove this user from this workspace. As you can see in this public…

Hi, @dstitt! Thank you for reaching out to Atlassian Community! I found this link from the official site of TortoiseGit: * https://tortoisegit.org/support/faq/#howremembercredentials and their doc has as an answer this StackOverflow thread: *…

Hi, Dominik! The Bitbucket account linked to the email you used to create this question and added this last comment doesn't have access to other workspaces, and it owns 2 repositories, none of them are over 1 GB. Even if it is a private repo, we from support should be able to see it. Maybe you are logged into Community…

Hi, @Irina Pykhova, The error message on the bounce that we removed was this: 554 5.7.1 [internal] recipient address was suppressed due to customer policy According to Sparkpost (our mail provider), it could be due to one of the following reasons: * The user clicked the list-unsubscribe header * The user clicked one of…

Hi, @[deleted]! Welcome to the community! Checking the repositories you own and have access to, I couldn’t find any that is oversized. Is this repository linked to the account you used to create this question? In case it’s not, could you please add a comment to this question with the account that has access to this…

Hi, @Sumathi Pundit, I saw that you created a ticket with our support related to the same question, so to avoid any possible misunderstandings or miscommunication that may arise from discussing the same matter on two different platforms, let’s focus on the ticket instead. Once the ticket is resolved, feel free to share the…

Hi, @fasc8! Thanks for your confirmation, I'm glad to help. Kind regards, Caroline 

Hi, @[deleted]! Thank you for reaching out to Atlassian Community! I can see you have access to another workspace that is under a free plan, which has 50 build minutes available per month. Checking the usage of this workspace, I can see that the current Pipelines usage is 61 minutes, so this is the reason the pipeline was…

Hi, @John Lawrence! Welcome to the community! Just to give you some context, this limit is set to prevent abuse, requiring us to validate if it's an actual person with a real need for that. I went ahead and exempted your workspace, so you should be able to create more than 30 repositories now. Please let me know how it…

Hi, Jeff! Thanks for your confirmation, I'm glad to know it worked. Kind regards, Caroline

Hi, @jeffstahlin! Thank you for reaching out to Atlassian Community! I checked our logs and confirmed that indeed, this email had a block on the server that prevented emails from being sent to them, so I removed the email from the suppression list. Just to give you some context around this issue, it can occur when the…

Hi, @jjordan1! Thank you for reaching out to Atlassian Community! In order to see the list of repositories under a workspace in the UI, you can click on your avatar in the upper right corner > open the workspace you would like to check > then, Bitbucket will redirect you to a page with a list of all the repositories that…

Hi, @Kajsa! Thank you for reaching out to Atlassian Community! I'm afraid Bitbucket Cloud doesn't have a feature for tag restriction at the moment (we only have the branch permission - restriction feature where you can restrict branches, but not tags). We do have an existing feature request to restrict pushing Git tags to…

Hi, @Kerry Carlyle! Thank you for reaching out to Atlassian Community! Could you please share with me where you see that a person who is not a member of this repo made changes to the code? The reason I’m asking this is that this could be due to a local git configuration. Some users who are members of the repo may have a…

Hi, @Sachin Pokhariyal! Welcome to the community! I checked our logs and confirmed that both emails had a block on the server that prevented emails from being sent to them, so I removed the emails from the suppression list. Could you please remove the invitations and send them a new one? You can do this by following the…

Hi, @jdugasMT! I'm glad to know the workaround will be useful to you and your team. 

Hi, @Dominik Panas! Thank you for reaching out to Atlassian Community! Currently, it's not possible to see the merge strategy of merged Pull Requests in Bitbucket Cloud, we can only see how the history of commits looks like. In this case, I went ahead and created a feature request to implement this on Bitbucket Cloud: *…