jredmond Atlassian Team

This is not currently possible in Bitbucket Cloud. (It looks like you were trying the BB Server API, which is different.)

That message shouldn't appear for repos, but it does appear for user or team profiles that are marked as private. Are you sure you have the complete address?

The "log in to contact Support" button at the bottom of https://support.atlassian.com/bitbucket-cloud/ is the best way, since it collects most of the relevant details. If that doesn't work you can email support@bitbucket.org and provide as much detail as you can.

You need to open a support ticket for this.

Are you asking about Siteground -> Bitbucket, or Bitbucket -> Siteground? If Siteground is blocking SSH connections to Bitbucket, then you should be able to use altssh.bitbucket.org port 443 instead. Your git and hg clones would then look something like this: git clone ssh://git@altssh.bitbucket.org:443/owner/repo.git hg…

You'll need to open a support ticket for this. Be sure to include details about which repo(s) you want deleted.

Bitbucket Cloud is currently only hosted in one region.

Your origins each have one underscore in the name, but the repo link you provided has two underscores.

Forks may start out with the same repository content as their upstream, but they don't automatically inherit permissions, default reviewers, merge checks, or other configuration details. (The general idea is that, if I fork a repo, then I get to decide how all the things work.) You'll need to populate the default reviewers…

It's the same deal with Bitbucket Cloud: https://blog.bitbucket.org/2014/09/16/introducing-pull-request-tasks/

That page explicitly describes that 10GB as being for LFS content, which is handled separately by both client and server. Non-LFS content is subject to the limits in the document Timothy linked.

If you're trying to get from your system to bitbucket.org, then the addresses listed on that page are all correct. HTTPS traffic to bitbucket.org is on the usual port 443, and SSH traffic is on the usual port 22. (There's also altssh.bitbucket.org, which listens for SSH traffic on port 443, but if you control the firewall…

bitbucket.org does not have port 7999 open, and it does not currently have a dynamic IP. Can you provide any more information about the problems you're seeing, and what exactly you've been doing to get them?

I'm not sure what you're asking here. bitbucket.org is Bitbucket Cloud; there is no repo storage on "Atlassian Cloud" other than Bitbucket Cloud.

That isn't how Git or Mercurial work, unfortunately - they're both designed around commits, rather than files. When you clone, you'll get every file in a repo, regardless of when it was last updated, and regardless of how many commits deep you go with the clone. (The concept of "last updated" also gets a little hazy with…

This indicates that your team doesn't own any existing repositories that aren't in this project. You can still add as many new repositories to that project, as long as you create them first.

You should have a "Transfer repository" option in the repo admin panel (on the "Repository Details" page).

That's effectively what pull does - only the commits since the last pull are sent over the wire, and they're applied to the client's working directory. Is there something else you're looking for here?

Do you have a local branch named "master"? You should see it highlighted in `git branch`.

Sorry, but this is a forum for questions about Bitbucket Cloud (https://bitbucket.org) and Bitbucket Server (https://www.atlassian.com/software/bitbucket/download).

That depends - do you want to see repos owned by the team, or repos owned by the user?

Bitbucket Cloud also supports Mercurial. I could also fail at subtlety and remind people that GitHub still doesn't support IPv6, but that Bitbucket Cloud does. Ditto HTTP/2.

@Intech Kalpesh, are you asking how to get updates for a single folder, or are you asking if it's possible to restrict access to folders within a repo? (The former is possible, as @Lonnie has helpfully answered, but the latter is not possible in either Git or Mercurial.)

This last line: debug1: read_passphrase: can't open /dev/tty: No such device or address as well as this line near the beginning of the session: Pseudo-terminal will not be allocated because stdin is not a terminal. both suggest that your key has a passphrase, and that you're trying to use the key someplace where you are…

Not currently. Can you elaborate on what you're seeing?

The username@bitbucket.org scheme is most useful if you're trying to use multiple accounts from the same computer - such as a work account and a personal account, or a contractor working with several different groups. You can still use git@ or hg@, though, and you can still use username@ even if you only have the one…

Is this Bitbucket Cloud (bitbucket.org) or Bitbucket Server? Are there any error messages when you try to use that hook? Are you using any AWS security groups to limit access to the SQS queues, and if so, are the relevant source IPs able to send? Is there any authentication necessary for the queue?

Your local network or ISP may be blocking connections to port 22 (SSH), but leaving port 443 (HTTPS) open. Glad to hear that you're still able to work over HTTPS, though.

"Connection refused" usually implies a network issue. Can you add any more detail?

That's Bitbucket Cloud, but (as Ana mentioned) you're looking at documentation for Bitbucket Server. Your screenshot shows a checkbox labeled "This is a private repository" - if you un-check that box, then the repository will be public, and anybody on the Internet will be able to read all of it (even without…