As for me, the ‘stop tracking’ operation is the one I use very often. It is different in SourceTree, as you can do operations on all files. GitKraken introduced in its 3.1 version the ‘view all files’ feature but you still can’t do any operations on the files. The second feature is, you can do anything to all the files in your project, not only to the ones in the work in progress area. As a workaround, you’ll need to create a temporary branch based on the commit you want to check out then switch to the newly created branch. I can right-click a commit and then press checkout on the context menu, by doing so, a detached HEAD will be created on that commit and I will be able to see my project at that exact version. The first one is the checkout commit, in the ‘Log / History’ view of SourceTree. There are two other features that I, personally, like in SourceTree. In addition, Git LFS is stable in SourceTree, however, in GitKraken, it is still in beta as of 3.1 version. This feature is very useful as many open source projects get contributions through submitted patches such as Linux and Drupal.
With SourceTree we can create and apply patches, something that is completely missing in GitKraken. At the top, we have the search button that we can use to look for commits. In the right panel, we can see details of any commit we select from the history, we can also stage, unstage, discard and ignore files from the work in progress and make commits from there, too. The project’s history and the work in progress are in the center, and we can see stashes too. In the left panel, we have information about the project, such as local branches, the remote repositories added to the project and their branches, stashes, tags, and submodules.
In GitKraken’s main interface, we have everything we need. When comparing their UI/UX, GitKraken has clearly the upper hand. In this article, I’ll compare them one to the other and show you the benefits of using them both together. I, also, used the CLI as well, so that every developer knows what’s happening behind the scenes when using their favorite GUI.īy doing so, I discovered that SourceTree and GitKraken are two apps that can live alongside and there is no need to choose between the two of them. When preparing the workshop, I opted for SourceTree and GitKraken for demonstrations as both are the most used GUI tools in satoripop. Recently, in satoripop, I led a workshop about Git aiming at introducing its best practices, demonstrating GitFlow and showing how we use it in our workflow.
0 kommentar(er)
