Mike Corsaro Atlassian Team

Under "Accounts" in settings you'll probably see a github account. You can try removing that and seeing if that fixes it. What version of Sourcetree are you using?

Hello! Sounds like you have the wrong keypair loaded, or the wrong key loaded in Bitbucket/locally. Make sure you double check and see if they match. Under "Tools > Options > General" there's a 'SSH Client Configuration' area where you can set your SSH key to load on startup.

If I had to guess -- is the repository on a network drive? If it isn't then you probably have an extremely slow HDD or something is causing your HDD access times to be more than 5 seconds for a simple "does this folder exist" check. If that check takes more than 5 seconds we consider it to be invalid and close the…

Hello! Sorry for the delay -- we're a very small team and it takes us some time to get around to everything. We'll be adding this feature to the installer for the next major release

Hello! So it seems there's some confusion as to what "HEAD" means. HEAD is a pointer to a commit, and in this case it's a pointer to that commit you switched to rather than the latest commit on a branch. Specifically, you're on a detached HEAD, which means any commits you make right now might get lost. The easiest way to…

Hello! The thing you're seeing is known as being on a detached HEAD. To fix this: * Create a new branch (hit the branch button) * Call it something like "Temp", make sure "Checkout new branch" is checked * When that's done, switch back to the master branch (just double click master in the sidebar) * Then, right click on…

Hello! Could you do 2 things for me? * Run a repository benchmark on the problematic repository (Repository > Benchmark Repo Performance...) and then upload that here * After doing that, try opening the Process Viewer (Tools > Process Viewer...) and then repeat the problematic behavior. Observe what's happening in the…

Hello! This will depend on your setup. Normally whenever you start a new feature, or bug-fix it's advised that you make a new branch for it. Then you'd normally merge that back into the "master" branch when you're done. However, you can also use branches for releases too -- whenever you do a release you should make a new…

Hello! Please see the reply to this question: https://community.atlassian.com/t5/Sourcetree-questions/Re-Sourcetree-can-t-pull-push-login-problems/qaq-p/955958/comment-id/26451#M26451 Thanks!

Hello! You should be able to change this via Tools > Options > Diff > Max Diff Line Count

Hello! You can use the extended integration to help Sourcetree automatically determine the correct URL for pull-requests on Bitbucket, locating existing clones fro links, and giving more accurate remote URLs for your repository.

Hello! This is a long-running problem with the git-credential-manager. To solve it: * Download the git-credential-manager 1.18.3:* https://github.com/Microsoft/Git-Credential-Manager-for-Windows/releases/tag/1.18.3 * Try installing Sourcetree 3.0.12*…

Hello! This is a long-running problem with the git-credential-manager. To solve it: * Download the git-credential-manager 1.18.3:* https://github.com/Microsoft/Git-Credential-Manager-for-Windows/releases/tag/1.18.3 * Try installing Sourcetree 3.0.12*…

Hello! This is a long-running problem with the git-credential-manager. To solve it: * Download git-credential-manager 1.18.3 * Install Sourcetree 3.0.12 * When prompted again enter your credentials OR add your account via OAuth in the Accounts tab in Options

Yeah -- the fix was back-ported and will be fixed in the next release (3.0.11) which should be released sometime tomorrow if everything works out 🙂

I see -- I thought you were using the context menu pull-request feature (right click on the branch in the sidebar). The "Push changes immediately" box exists so you can push automatically after commiting (if you had "Create Pull Request" unchecked). Working on master and merging into master won't do anything because…

Ah okay. Just a FYI:

To provide an update on this: we've identified an issue with the syntax highlighting library we're currently using and have submitted a PR to address it. Once that gets approved we'll update and release a hotfix. Thanks!

Are you sure you didn't push to the repository? We haven't seen any other users seeing a push happen when a the PR link was opened. Did you check the commit log in Bitbucket to see when that commit was actually pushed?

Looks like the issue is caused by syntax highlighting. As a work around go to Settings > Diff and turn off syntax highlighting. I'll investigate further to see what the issue is. Thanks!

Okay, so there's nothing wrong with the URL. Could you open the file "you repository/.git/sourcetreeconfig.json" and check the value "BaseUrl" under "RemoteProjectLinks" and ensure there isn't an '/' at the end?

* Open the repository * Click "Settings" in the main toolbar with the gear icon * Double-click/edit the "origin" item * Check the "URL / Path" and post that here * Optional: change the "Remote Account" to use the Bitbucket account you added previously.

This is probably an issue with the git-credential-manager. Try downloading v1.18.3 here which should fix it.

Ah, okay. That's probably caused by ST struggling to render the diff. Could you email me the file so I can profile it (mcorsaro at the company name this website is run by.com)? It would be very useful in solving this -- thanks!

Do you get the BugSplat error dialog when it crashes? If so, could you supply the crash ID or the dump file? Thanks!

Could you try 3.0.9 and see if that fixes it? Thanks!

Hello! Could you give me more details about the file? How big is it? Are there any lines that are extremely long? Thanks!

Hmmm... seems like you might need to add the absolute path to the LabVIEW exe in the parameters? Could you try the following? \"C:\program files\PATHTOLABVIEW.exe\" \"$BASE\" \"$LOCAL\" \"$REMOTE\" \"$MERGED\"

Hello! There was a bug in custom diff tools recently that caused this to not work quite right (you can find the fixed version here) After updating, you should be able to try the following: "External Merge Tool" set to "Custom" "Merge Command:" set to: PATH TO 'LVMerge.exe' goes here "Arguments" set to: \"$BASE\" \"$LOCAL\"…

Hello! Could you check which version you're on (Help > About)? There was a bug where we accidentally added an extra '\' at the end of 'bitbucket.org' when making a PR that was recently fixed. Thanks!