Tyler T Atlassian Team

An easy way with Postman would be to create an App Password and add it to the credentials settings under Basic Auth. https://bitbucket.org/blog/app-passwords-bitbucket-cloud

Right now you can add custom values to those 4 fields.

Hi @pankaj4-singh if you are using Bitbucket Cloud, try clicking the Lost codes? link on the 2FA login screen to recover your account.

Hi @Robc and welcome to the Community! As part of the Bitbucket Cloud Mercurial deprecation, pushing to repositories has been disabled as of this month (July 2020). There are more details here about the deprecation here: https://bitbucket.org/blog/sunsetting-mercurial-support-in-bitbucket

@Isaac Van Arnem if you login to your account using Google, you can create an App Password to authenticate with git operations. Here is the official documentation: https://support.atlassian.com/bitbucket-cloud/docs/app-passwords/

Under Repository settings > Branching model you can update the default names of the different branching model names.

Here is some information about creating App Passwords: https://support.atlassian.com/bitbucket-cloud/docs/app-passwords/

Hi @Julia Sachs and welcome to the Community! Your email address ended up in a bounce list but I've removed it. Please try sending the email again.

You can create an App Password specific to git operations or whatever permissions you need. Here is the documentation: https://support.atlassian.com/bitbucket-cloud/docs/app-passwords/

@Scott Guymer I've sent you an email about this.

Thanks for your feedback! I will share it with the team.

When your team visits the URL for the workspace like: https://bitbucket.org/<workspace_slug>/workspace/snippets/ What is the issue?

Hi @Roberto Barreto , it looks like your email had previously bounced and was put into a bounce list. Can you please the password reset flow again? The email should come through this time.

Here is some additional documentation: https://www.atlassian.com/git/tutorials/syncing

What do you get from git remote -v It should be the address to your repository and look something like this: origin git@bitbucket.org/<workspace>/<repo_slug>.git (fetch) origin git@bitbucket.org/<workspace>/<repo_slug>.git (push) If not, you can update your repository URL using this tutorial: Creating and modifying git…

To get all workspaces, try this workspaces endpoint without the permission filter. https://api.bitbucket.org/2.0/workspaces

Sorry about that! Please create a ticket with our support team so they can look into this issue further: https://support.atlassian.com/contact/#/

Changing those commit messages will rewrite history. Here is some information about updating commit messages: https://git-scm.com/book/en/v2/Git-Tools-Rewriting-History

Is there an error? Can you try logging out of your Atlassian account and then try to log into Bitbucket?

Can you share a screenshot of the error? Normally if they don't have access to create a snippet in the workspace, then the workspace will not appear in the dropdown. Thank you

Does this page load for you? https://bitbucket.org/account/settings/username/change/

In your workspace settings, you can visit the Users on plan view to see which users have access to repositories and then manage their access using the links next to the user. 

Ok.. go to the workspace and click the members tab. * Select Manage users * Select the group you want to manage * Click the Edit button * Change Default repository access to Read * Uncheck the permissions to Create Repositories and Administer Workspaces

Bitbucket Server does not have the same size limitation of Bitbucket Cloud since it is self-hosted. 2TB can be managed via Git LFS but it might not be the best solution depending on your needs and average file size.

If a developer needs to update a common file that also needs to be updated in all the other branches, the recommended approach would be to: * Create a branch with the change to the common file * Merge that branch into master * All the other branches should pull the latest version of master to get the change

Do you want to make them public? The first step would be to remove all the users with admin and write access - or change their permissions to read.

Find your workspace - it might be the same name as your username. * Select Settings * Select Users on plan There you will be able to manage users that have access to your workspace and its repositories.

If you have builds configured, there should be a build status icon on the lists of commits. Do you have builds configured on the repository in the second screenshot?

The image on the left is from Bitbucket Server. The prevent changes without a pull request on Bitbucket Cloud, you can do the following: * Add branch 'master' (you already did this) * Keep Write access blank * Merge via pull request -> add Everybody or specific groups After you save, nobody change will be able to write to…

Thanks for the reply. I will let the team know that pre-filling the project would be a helpful improvement. Regarding content ownership, that FAQ explains that the change was prompted by new GDPR privacy rules. "Should not own" means that you can create a repository and your username is not visible in the URL, which…