tipright.blogg.se - Sourcetree git flow slow

#SOURCETREE GIT FLOW SLOW FULL#
#SOURCETREE GIT FLOW SLOW WINDOWS#

Its possible to open multiple windows if that’s what you need.

#SOURCETREE GIT FLOW SLOW FULL#

The full path to the repo is shown in the Window title. Labels are poorly written too, which makes it scary for learners) (Sourcetree hides most of the git internals, so you need to experiment. Tool tips on some buttons show what git commands will be executed when you press them (this helps you learn git). (The workflow in Sourcetree is vague and unintuitive) The work flow for resolving merge conflicts is very streamlined: (In Sourcetree there are many clicks and confusing options, and its so slow performing the clone) The rebase commands to abort or continue are hidden 2 deep in a menu.)Ĭloning a repo is wonderfully simple - you can do it in two clicks: (Sourcetree doesn’t have clear indicators that a rebase is in progress. You can refer to the last git command, and there are buttons to Abort rebase or Continue rebase. The GUI has clear indicators to show when you are currently rebasing. (The Interactive rebase interface in Sourcetree is vague and unintuitive) Simply select one or more commits, then use the context menu to squash, reorder, drop, amend commit message, etc. Interactive rebase commands are performed individually, and this works out to be very intuitive from a GUI. (Sourcetree can do this, but its unreliable and usually doesn’t give the correct result) The entire interface is consistent and elegant.Ĭtrl+ Click any two commits to see a diff of them. Please also head over to their website and read the feature highlights. Sublime Merge is a great tool and its features helped me learn git and made my workflow faster.īelow I’ve explained each awesome feature, followed by a comparison with SourceTree. After switching to Sublime Merge my knowledge of git exploded and it has been a great discovery process. I have used Sourcetree for over a year and during that time I was still learning git. Sometimes when you click on a branch it doesn’t jump to it in the graph view. Regularly prompts for authentication for each repo separately (very frustrating). Regularly complains about corrupt dictionaries and asks if I want to delete them. Regularly crashes and needs to be reinstalled (or requires a reboot), usually just after updating Microsoft Office. Note: my experience is with the Windows versions of Sublime Merge and Sourcetree. I hope my comments help to further improve both tools. The main point of this article is to point out the amazing features in Sublime Merge, and to illustrate why you should avoid using Sourcetree. Copy any relevant output.Sublime Merge vs SourceTree (Git client comparison) Mac: Open "Console" application and search for "SourceTree".Windows: C:\Users\\AppData\Local\Atlassian\SourceTree\sourcetree.log.Can you run 'git status' on that repository?.

If you have a lot of untracked files, please make a note of this also.

The file filters you're using in SourceTree, i.e.

How many repository windows you have open at one time.

How many repositories you have in SourceTree.

locally, on a mounted volume or over a network (SMB share etc.)

Where your repository is located, i.e.

System resources, CPU/RAM/HDD capacity (+ available hard disk space).

Whether it's for Git/Hg and which version (embedded, system, and what system version if system).

open in an editor) when trying to perform Git/Hg operations on them

Ensure files in your repository aren't locked (i.e.

Make sure there's no applications constantly writing to disk at a repository location, this would cause SourceTree to constantly refresh.

Calling Git/Hg from the terminal performs as expected i.e.

on your hard disk rather than over a network or mounted volume.

That the repository location is local, i.e.

That you've got an up-to-date copy of SourceTree (we no longer publish to the App Store!).

Make sure you have plenty of system resources available, CPU, RAM, plenty of hard disk space etc.

If you're using a system version of Git/Hg, make sure it's a recent version.

If you have a lot of untracked files, make sure the filters in SourceTree don't show these as Git/Hg take a long time to respond.

Things you can do to help SourceTree's performance Before you ask support or developers it would be helpful if you could go through the following list to help narrow down what the problem is, as well as a list of items to provide to support in the event of poor performance.

There are a number of reasons that SourceTree may be performing poorly.