I love the idea of a Repository Manager, because this is what I am looking for. But still for my very personal way of working, there was one tool that stood out a bit: Fork. My personal recommendation: ForkĪs written above, different ways of of working, different recommendations. People seem to like GitKraken for its DarkTheme (really is that so important). Looking then on stackshare.io, we do not get much more material for a clear recommendation. If I had to choose a favourite, it is this one.

Fork is again a tool which is good for handling many repositories and also provides a good intuitive way to explore the past and the current uncommitted changes.

Finally Sublime Merge, Sourcetree and Github are neat, but very much focussed on single repository handling.

SmartGit seemed to be a bit too rigid in the UI handling, but delivers good overviews and comparisons.

Tower is the tool for managing many local repos as you can import all and group them, but if it is them exploring the history, for me at least it seems that other tools were a bit nicer.

One tool (GitUp) shines with visualization - It displays the history better than any other tool, but the rest is basic.

We have one tool(Gitkraken) that tries to be a bit more different and tries to integrate some more own features.

It is difficult to recommend a best tool. I announced proudly that I would recommend a tool instead of just listing them up and say the usual it depends. But then again, the same thing to others. It does a solid job in exploring the past and changes. GitUp is a tool that shines with this visualization. In 2005, I dropped out of my ClearCase project and in all subsequent projects I did - no matter if it was Subversion, TeamFoundation Server or Git, I was missing the ClearCaseExplorer. I had some experience with other tools as well, such as Visual SourceSafe, but ClearCase was the tool I was using for two years and I loved it. Exploring History: Who did what in the past?.Git Commands: Applying commits, pushes and other common commands on a repo.Repository Management: The ability of a tool to manage multiple repos.

While I was exploring the tools, I also realized that I should group into two features: I did a bit of Googling and looked which tools come up often. Therefore, I decided to look for a tool that manages my repositories. It does not help much to delete local repositories regularly. So, all in all, it creates a bit of an effort to keep an overview of what is on my machine.

If I work within a guest VMs, I normally mount this workspace directory. Labs are highly personal, but still I keep most of them in repos. So, for instance when I started to work with Jenkins X, I create a repo there.

lab covers everything where I try to explore a new technology.

So I created various Linux VMs that I experiment with. Although I am used to work with the cloud, I simply love to have some development servers on my iMac.

devops is all my efforts of automating my own infrastructures.

edu contains all my work for universities and where I write articles.

com directories contain projects I do for companies.

I have one workspace directory where I have several sub directories. But even if I group my projects with tags and naming conventions, sometimes on my hosts it gets messy.

Fork vs github desktop vs tower