![]() So that we can record this merge action to our history. Usually, I will recommend to tick the 3rd checkbox in the settings: 'Create a commit even if merge resolved via fast-forward'. Here, you can choose which commit you want to merge from. User can also merge other branch to your local branches, by clicking at Merge, a modal will appear: Usually I will not change the default settings and just click OK, but you also can change settings if needed. If developers want to pull, they can click at Pull, a modal will appear When clicking at Commit Options dropdown, developers also can have other advanced features, for example Bypass commit hooks to bypass husky hooks. (by ticking the checkbox 'Push changes immediately to origin/.') ![]() Here, you can choose which files you want to stage in this commit, together with their changes showing on the right hand side.ĭevelopers can input the message for this commit, as well as choose whether should this commit be pushed to remotes after clicking the Commit Button. Clicking Commit will lead to Commit stage: If you have uncommitted changes, it will popup the number here. When you click at the stashes, you can see what is the changes belong to that stash.ĭouble click at the stash to apply the stash into your local. Here you can see all of you stashed stashes, with there corresponding names and branches. Here you can see all the remotes branches. Here you can see all the tags belong to this repo. ![]() In the commit history box, you can also see the tags, branches that mapped to this commit. The current checking branch will be bold. Here you can see all the branches you already checked out. In the tracking box below, when developers click at the files, they can also see the difference in the right hand side. If you click at any committed commit on remote in the history box, the tracking box will corresponding display the changes in that particular commit. Developers also can tracked which files already staged/not staged. When you click at this Uncommitted Changes, it will showed all the uncommitted changes in your local in the tracking box below. You still can continue using Git terminal or any other Git UI clients, as long as it best fit with your coding style and productivity. This article is just served as a preference and recommendation from the point of view of the author. With the help of Sourcetree, developers can easily visualize the git workflow and manage their git history, git action better. Every day, our software engineers have to work with Git to push local code, pull remote code, merge with colleagues’ code, and resolve conflict, … This article aims to give a quick introduction to a Git UI Client, named Sourcetree. In a company, we use git and GitLab as the source code management tools.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |