Caroline R Atlassian Team

Hi, @Yusuf Temiz! Welcome to the community! I confirmed that the account associated with the email you used to create this question is linked to a Bitbucket account that is empty (has no repositories). However, there is another Bitbucket account linked to the username you shared with us (I removed this information from…

You're welcome, @chernandez_energy! Feel free to reach out if you ever need anything else. Kind regards, Caroline

Hi, @Mathijs ! Now I create a branch in which I remove deployment: production from bitbucket-pipelines. I assume that you edit the yaml file and remove the deployment: production in the new branch you create, is that correct? If this is the case, you are correct. It will be possible to run pipeline branches:master for this…

Hi, @paul.liu! I performed an analysis on our logs and verified that the email you shared with us had a block on the server that prevented emails from being sent to this recipient. This can occur when the system tries to send an email to the user and the account does not exist yet, is not activated, or it rejects the email…

Hi, @Hardik Patel! Currently, you can restrict access to a repository in general or prevent users from pushing content either to the repository or to a specific branch with the write access permissions and branch permissions respectively. We don’t have a feature to prevent access to view specific folders in a repository,…

Hi, @SJ Office! Welcome to the community! It’s not possible to migrate only selected commits from GitLab to Bitbucket. However, you can give this user access to the repository on Bitbucket, this way they can commit the changes to the new repository. So, this is what I would suggest: * Give this user access to the…

Hi, @Martin Richards. I haven't been able to reproduce this behavior, I tried testing this in one of my repos and the side-by-side diff is working as expected. In this case, I would like to ask if you could provide us a screenshot of the error you are facing, but without the URL and any personal information, so we can…

Hi, @chernandez_energy! Welcome to the community! I ran the GC against your repository and managed to reduce its size. To give you some context around the git GC process, Bitbucket triggers a garbage collection on the repository after each push, however aggressive GC is triggered by GIT once the unreachable/dangling…

Hi, @jcarnuccio. After looking into it and similar reports from other users, this looks to be a bug with Git 2.32 and the credential manager, as you can see here: * https://github.com/microsoft/Git-Credential-Manager-Core/issues/364 And as you already found out, downgrading the Git version is a workaround, until this issue…

Hi, @Vivek Kaul! When you upgrade the plan on a Bitbucket account, you do it to a specific workspace. So, if you create a new workspace, it will be under a free plan, this is the expected behavior. However, you can create different groups with specific access to the repositories and to manage the workspace. This way, the…

Hi, @Hardik Patel! Welcome to the community! I saw 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. Feel free to share the…

Hi, @Andrey Baevich! Welcome to the community! In order to be able to create a repository under a workspace, the user needs to have the "Create repositories in this workspace" permission. In this case, you can either edit the group you have created or create a new group and select this option. You can follow the next steps…

Hi, @Mayank! We performed an analysis on our logs and confirmed that the email you shared with us (I removed the email you mentioned from your answer for security reasons) had a block on the server that prevented emails from being sent to this recipient. This can occur when the system tries to send an email to the user and…

Hi, @Manish Kumar! Welcome to the community! Currently, we don't have a way to add a secret while creating a webhook in Bitbucket Cloud. However, we do understand that this would be an important feature, so we already have an open feature request to include webhook secret in Bitbucket, as you can check here: *…

Hi, @DFCC team. 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. Feel free to share the resolution here to help other…

Hi, @Enoch Selvaretnam. In 2016 we introduced Atlassian accounts, and ever since log in to Bitbucket is only possible with the primary email of the account: * https://bitbucket.org/blog/atlassianaccount Due to our privacy policy, we cannot disclose the email of a Bitbucket account if the email you used to reach out to us…

Hi, @Gaurav Panchal. It is possible that the timeout occurs if the PR diff is above the limits. Currently, the limits on diffs for pull requests are: * A file's diff cannot exceed 2000 changed lines or 102,400 bytes (100 KB) of raw diff data. * The entire diff cannot exceed 8000 changed lines. * The maximum number of files…

Hi, @[deleted]. Indeed, in our Pull Request limitation doc, we indicate that "When the limits listed above are reached, the pull request loads files individually. You can navigate between files by using the file tree in the right sidebar or the navigation buttons in the header." So, in case you reach those limits, you…

Hi, @Abhinav Bezgam! Welcome to the community! I saw 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. Feel free to share the…

Hi, @[deleted]! Welcome to the community! I understand you are not been able to see the diffs on the Pull Requests to the develop branch, is that correct? If that's the case, as the diffs can become very large, we have some limits on diffs for pull requests: * A file's diff cannot exceed 2000 changed lines or 102,400 bytes…

Hi, @jcarnuccio! Welcome to the community! 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. Feel free to share the…

Hi, @mishmarot.dev001! Welcome to our community! Could you confirm if the "Something went wrong" message is appearing for the whole page, or only for the diff of the Pull Request? If it's only showing to the diff, could you please check if the diff of the PR is within our limits? * Limits for viewing content and diffs If…

Hi, Claude! Indeed, the https://prguidelines.services.atlassian.com is currently unavailable because the PR Guidelines functionality was discontinued on June 8th. The decision was made due to low adoption and usage. The discontinuation was announced in the following article: PR Guidelines Functionality Discontinuation…

Hi, Federico! 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, Vivek! I have confirmed that you had 2 repositories above 1 GB, so I ran a git GC on both of them through the server. I was able to reduce the size of one of the repositories, but the other one is still over 1 GB. Just to give you some context around our repository size limit, we do recommend repositories be kept under…