![]() If you are looking for a modern and visually appealing user interface, GitKraken is a good option. The best choice for you will depend on your individual needs and preferences. On the other hand, Sourcetree is generally considered to be lightweight applications that can run more efficiently on older machines. Performance: Compared to Sourcetree, GitKraken is recognized for its relatively high resource consumption, which can cause performance issues on older or less capable computers. Sourcetree is owned by Atlassian, the same company that owns Bitbucket, and is optimized for use with Bitbucket and other Atlassian products. Integrating with Git hosting services: Gitkraken offers integration with a wide range of Git hosting services, including GitHub, GitLab, and Bitbucket. ![]() Pricing: Gitkraken is a commercial product which offers a free test period, after which users must purchase a licnese. The preference for either interface may vary among users, with some finding Gitkraken’s interface more appealing, while other may prefer Sourcetree’s interface due to its familiarity and ease of use. User Interface: The user interface of GitKraken is designed with a modern and visually pleasing approach, whereas Sourcetree’s interface follows a more traditional and utilitarian design. However, there are some key differences between the two tools. If you are interested in it, use my referral link to try GitLens or other GitKraken products for Free! gitkraken.Gitkraken and Sourcetree are both Git clients that can be used to manage Git repositories, visualize changes, and resolve conflicts. Let me know if you think these features could be helpful to you too or if you already use them in your daily work. I hope you have other tips for improving your productivity with git using GitLens. Obviously, you have to indicate two references for the comparison.įor me, this is really convenient when I have to compare two different versions of the code in the past or to check when and why a piece of code has changed. Clicking the button "Compare References" appears a new VsCode command, where you can type the reference of your branches/tags or commits. With this view, you can check the commits and see the files changed in those commits.Īfter the search could be necessary to compare two commits, you can use the other button called "Compare references" to do that.Īlso, this feature is easy to use. After that, in the GitLens panel will appear the results of the search. If you click the button, the extension opens a command with different options you can select your choice and type your terms. Typically, in my case, I use this feature to find an old commit by message or by author. Using this feature, you can search for a commit by different filters: commit message, author, SHA, file or changes. To do that, in the GitLens bar, you can find an option called "Search & Compare". This view is also available using the icon with the git logo in the top right of the file, and you can toggle this view by clicking it easily.Īll these features are fantastic, but sometimes we need more, for instance, searching for a commit or comparing two different commits. Instead, If you click on the second part (that is relative to the other authors of the file), GitLens opens a new bar on the left of the file and shows, for each line, the last commit relative to it, so you can understand who and why someone has changed the line. This is very helpful if you want to get info quickly about the changes in the file. The first part opens the VsCode command with some possible actions to see the commit you can see all the files relative to the commit, open the commit detail, and see the commit in the commit-graph. You can click on the part relative to the last commit or the other one. ![]() In addition, there is also info on the number of people that touched the file. First, at the top of your file, you can get info about the last change and the name of the person who pushed that commit. With GitLens, you can get much info about your current file without losing focus on it. When you work with git, you want to get info about commits and who changed the codebase quickly.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |