I’ve met the same problem and here’s how I solved it: (Assume your project is not already under local source control) Create a new project under LOCAL source control (Please note that adding remote source control at this stage may not be successful) Make this new project a clone of your old project – drag … Read more
In my case, the git repository was duplicated somehow in the config file: cat .git/config gave me: [remote “origin”] url = git@bitbucket.org:myUserName/myRepositoryName.git/myRepositoryName.git fetch = +refs/heads/*:refs/remotes/origin/* As you can see, myRepositoryName is duplicated, so I removed that, and now the config file looks like this: [remote “origin”] url = git@bitbucket.org:myUserName/myRepositoryName.git fetch = +refs/heads/*:refs/remotes/origin/* Doing this, my … Read more
None of the above worked, I had to do: File -> Invalidate Caches/ Restart Upon restart it re-indexed all files and everything worked again as expected.
I have done below mentioned things and it started working. vim ~/.ssh/config Add these lines and save it. Host bitbucket.org Hostname altssh.bitbucket.org Port 443 For Windows: Go to the place where your .ssh folder is located (run %USERPROFILE%). open the .ssh folder and create a file with the name config without any extension. Paste the … Read more
I’m using git(2.12.2) 64-bit on Windows 10. My solution is simply close the login window which you have to type account and password, and a SSh window will pop out, then you type your password.
Turns out the issue here was that I was using the URL for the repository displayed on my Bitbucket repository’s page, which includes the username in front of the bitbucket domain name, so it ended up looking like https://myusername@bitbucket.org/myusername/myrepo. Apparently, when the username is provided in this way, it ignores what’s in the [auth] section. … Read more
We think we had the same problem today and were able to solve it without contacting Bitbucket support, as below. Note that the method discards last commit from the repo – so you probably want to have its backup. Bitbucket reported that our repo was about 2.1GB, while when cloned, it only took about 250MB … Read more
If you don’t need to pull the whole history you could specify the number of revisions to clone git clone <repo_url> –depth=1 Of course this might not help if you have a particularly large file in your repository
Try: git clone git@bitbucket.org:project/project.git -b develop_one –single-branch For already cloned repos use: git fetch git checkout develop_one # Or more specific: git checkout –track -b develop_one This will track the develop_one branch from the remote.
npm install git+ssh://git@bitbucket.org/{user}/{repository}.git