Comments
-
Hello! Which version of Windows are you using? Please make sure any anti-virus or anti-malware is not interfering with the installer. Thanks!
-
Hello! This is probably a bug -- I'll take a look at it on Monday and report back.
-
Sourcetree 3.3.6 is being progressively rolled-out now, but you may manually download it here.
-
Hello! This is a false positive. For all released builds we scan both applications using Symantec Cloud Workload Protection for Storage, and for a fallback we use ClamAV.
-
Apologies for the delay on the next update with this fix. I’m expecting QA testing to be complete this week and the rollout to begin hopefully next week. Things have been a bit hectic around here. We’ve got some exciting things to share soon.
-
Check default remotes for updates every 10 minutes This is a bit misleading. It doesn't actually ping Bitbucket Server, it actually just runs some git commands: git fetch origin (get new remote branches) git branch -vv (get the ahead and behind count for branches) Will it record the access logs in Bitbucket server? I'm not…
-
@Jared Steffen: what errors are you receiving from ST and the terminal? @Dim Entelis * You can file a bug for Bitbucket here * You can file a bug for Jira here * If you're paying for Bitbucket or Jira, you can get support here
-
You’re having crashes, or just the repo avatar thumbnails are not working? Don’t want to use Sourcetree? Just hit the “terminal” button and run the commands yourself 🙂
-
Hello! How big are the files you’re deleting? Can you also check the memory of the git process that’s running? Also, try toggling the “Disable Libgit2” too. If you have a big repo libgit2 will have to load that into memory. Working set memory is generally a misleading metric. It includes memory shared by other processes…
-
Hello! Have you tried using embedded git? It appears that git isn't set in your environment path -- could you try installing the latest version of git and check the "add git to your PATH" setting?
-
Hello! Which OS are you using? We enforce this behavior because the docs actually warn about this topic: Warning: Running git merge with non-trivial uncommitted changes is discouraged: while possible, it may leave you in a state that is hard to back out of in the case of a conflict. Due to this, I'd advise that you…
-
Hello! Are you using Mac or Windows? On Windows, we've done some work on improving this, but it could be better of course. First, you'll want to: * Make sure you're using the latest version of Sourcetree (3.2.6) * Make sure you're using the newest version of Git, and that Sourcetree is using System Git* You can find that…
-
Do you have any IT-policy settings set for Chrome? What version of Chrome are you using? Do you have javascript or some plugin that is breaking Bitbucket? I just tried it in Firefox, Chrome, and Edge, and they all work fine. Do you have some anti-virus that's preventing communication on "localhost"?
-
Ah, that's because it's not possible to automatically use your Github or Bitbucket account as the default author info for commits. You need to manually override it per-repo, or use one common name and email.
-
Hello! Which OS and version of Sourcetree are you using? If you're using SSH, could you please verify the URL for the repo you're trying to clone starts with "ssh:" or looks something like "git@gitlab.com:blah/blah.git"?
-
Hello! You can fix this issue by setting a username and email address in the Options menu (be sure to check the "Allow Sourcetree to modify your global Git and Mercurial config files" setting too). You should see your username and email set on the commit screen:
-
Hello! You can fix this issue by setting a username and email address in the Options menu (be sure to check the "Allow Sourcetree to modify your global Git and Mercurial config files" setting too). On the commit screen you should see your name and email set.
-
Hello! Which OS and version of Sourcetree are you using? Are you cloning from Bitbucket, or Github?
-
You might be able to work around the issue by setting a username and email address in the Options menu (be sure to check the "Allow Sourcetree to modify your global Git and Mercurial config files" setting too).
-
Hello! This issue has been fixed for the next release, sorry about that! I'm expecting to have it ready for beta this week, and it should be released sometime soon.
-
Hello! Unfortunately you'll need to have Sourcetree connect to the internet, but you'll only need that for the initial login. Once you login you can use Sourcetree offline without any limits.
-
Hello! I'll need more details: * Which OS are you using? * Which account are you logging into? Bitbucket? * What are you attempting to do? Login to Sourcetree, or push a branch, or commit code? * Have you tried using OAuth for login rather than username and password? * Have you tried using SSH rather than a username and…
-
Hello! Sounds like there's something corrupted with the repo itself. Can you commit from the command line? If you run the following command does it work? git commit -a You can run commands manually by opening the repo and clicking "Terminal" If that doesn't work, you'll probably need to delete and re-clone the repository.
-
Hello! Please update your version of git. You can do this by either: * Downloading Git from the official website * Running Sourcetree and navigating to "Tools > Options > Git" and click "Update embedded git". If you do this make sure you've switched to using embedded git
-
Hello! I'll need some more info -- what happens when you attempt to install Sourcetree?
-
Hello everyone! This will be fixed in the next release, which should be in beta very soon. This was caused by a small change that moved deleted files in the working copy to the recycling bin, but ended up applying to all removed files.
-
I suspect something odd is happening. Can you have your colleague do the following: * Open "Tools > Options > Git" * Try checking the "Disable LibGit2 integration" checkbox and see if that changes anything If that doesn't fix it, then try and do the following: * Open the process viewer -> "Tools > Process Viewer" * Open…
-
Hello! Your colleague might not be on the same version -- there was an issue with this in v3.2.5. You can manually download 3.2.6 here, or open Options > Updates and check for the new update which is now available to all users. As a workaround if you're not able to upgrade: uncheck and then check the "push" checkbox in the…
-
The WMI service has some issue, which might be related to the update. You'll need to repair the WMI service -- a guide on how to do that can be found here
-
Hello! You'll have to adjust the remote host settings for the repo. There's 2 ways you can do this: If you already have a Github Enterprise account added to Sourcetree: * Open the repo * Hit the "Settings" button * Click "Edit" on the remote URL * Under "Remote Account" select your Github Enterprise account * Click OK If…