Tyler T Atlassian Team

@James Brantly , work is starting on this soon. Please follow the public ticket to track the progress: https://jira.atlassian.com/browse/BCLOUD-7968

Hi @Anthony Jocius and welcome to the Community! Do you have experience with git? Any code project, large or small, will find benefits using git for version control and saving backups of files in an organized way. You may find that Bitbucket is a good fit for your project when using git. Learn more…

Hi @Pete Mantell and welcome to the Community. We have raised a public issue to track this bug: https://jira.atlassian.com/browse/BCLOUD-20870 There you can subscribe to updates and contribute additional feedback.

Nice post!

Hi @Busra Doyran and welcome to the Community, Usernames do not appear in URLs for privacy reasons. If you want the URLs to update, you will need to update the ID of your primary workspace. The URL will look something like this: https://bitbucket.org/<your_workspace_id>/workspace/settings/change-id After you change the…

Please reach out to support. There is a possibility the repository was flagged as malware, etc. but support can look into it further for you: https://support.atlassian.com/contact/#/

Hi @Pushpendra Tripathi , what error are you seeing? There might be an issue where the username you have chosen is already taken.

Thanks for the information. Are you using a mouse/trackpad or keyboard? Or both? We are looking into this now.

Hi @fouratj , sorry about the issue with the file tree. Are you able to scroll inside the sidebar? What OS and browser are you using? We'll look into this ASAP.

Transferring does not copy the repository, it moves it by assigning it to a new owner (the new workspace). To answer your question, the "original repo" becomes obsolete since it no longer exists in the original workspace - the new home will be the new workspace. If you want to copy the repository, you can clone or fork it…

There isn't a hard limit but you may want to consider using projects to organize repositories. However, workspaces would be a good fit if you need to grant clients access to many repositories in a single workspace. What limit do you consider high? 

Hi @Sebastian Brudziński , The Bitbucket Cloud team is dogfooding a feature called Default Pull Request Tasks right now. With it, you will be able to specify a list of tasks to include on every pull request. You can vote for and follow along the public issue here: https://jira.atlassian.com/browse/BCLOUD-19846

Does your repository need to be a fork? If you are not using the forking workflow, then you could clone the original repository (instead of forking it) and the default destination branch for pull requests would be the cloned copy rather than the original that was forked.

In this tutorial, in the first screenshot you can see that there is a dropdown for the target branch: https://support.atlassian.com/bitbucket-cloud/docs/create-a-pull-request-to-merge-your-change/ After you change the target branch, the diff will update.

Take a look at merge checks https://support.atlassian.com/bitbucket-cloud/docs/suggest-or-require-checks-before-a-merge/

What is your question? Here is some documentation about pull requests: https://support.atlassian.com/bitbucket-cloud/docs/create-a-pull-request/ Create Tasks for things that must be addressed for approval to help designate between suggestions and discussions and things that must be fixed.

A fork is a bit different than a cloned copy of a repository. When used in apps like Bitbucket and Github, forks establish a relationship between repositories. When that relationship is established, one can create pull requests from a forked repo back to the original repo. This can be done on the command line using `git…

If Repo A allows forks, you should be able to create a pull request from Repo B against Repo A. This documentation has more information: https://support.atlassian.com/bitbucket-cloud/docs/fork-a-repository/

@Julio H. you can add suggestions to the public Jira project: https://jira.atlassian.com/projects/BCLOUD/issues/BCLOUD-13142?filter=allopenissues

Workspaces are simply a way to organize repositories. Members can be added and removed from workspaces. There is no root workspace. Perhaps you can use 1 workspace for your organization and then organize repositories into Projects instead? You may find this Workspaces FAQ…

If someone can clone a repository, then they have access to view the commit history. By cloning a repository, they are downloading it to their computer. That is how git works and not unique to Bitbucket Cloud. A user cannot have read access to clone a repository without having read access to the repository on the Bitbucket…

Yes, if the user has permissions they can clone without using the website. They will need to know the repository URL or workspace ID + repository slug. Here is some additional documentation for cloning repositories using git: https://www.atlassian.com/git/tutorials/setting-up-a-repository/git-clone

One option would be to fork the main repository which will preserve the history. The fork will create a copy. Each repository will have its own history unless you are using submodules. Another note - be careful when storing password in git repositories. It is generally not recommended. This thread has some additional…

Go to repository settings: https://bitbucket.org/<workspace_id>/<repo_slug>/admin In the upper-right corner there is a Manage repository dropdown menu which has the transfer option.

Here is some additional information about the incident: https://bitbucket.status.atlassian.com/incidents/c82sx43p72lk

https://bitbucket.status.atlassian.com/incidents/c82sx43p72lk

https://bitbucket.status.atlassian.com/incidents/c82sx43p72lk

https://bitbucket.status.atlassian.com/incidents/c82sx43p72lk

https://bitbucket.status.atlassian.com/incidents/c82sx43p72lk

Hi @eladb and welcome to the Community. You can manage your avatar in your Atlassian ID account: https://id.atlassian.com/manage-profile/profile-and-visibility