Right click and choose Reset master to this commit. In this case, you should do a Soft Reset. The requirement here is to reset to the commit where we Added line 6 and NOT lose the changes after that (like Line 7 & 8). Repeat this exercise three times, so that you have a history similar to the following: So, let's add a line to the 1.txt followed by a commit. You can set up your preferences in SourceTree so that it doesn't push automatically. This time, you will find that the message appropriately changes without creating a split in the tree structure! You get the goodness of git locally, without changing the remote yet. Notice that the check box Push changes immediately to origin/master is NOT checked.
Using sourcetree and bitbucket to create repositories how to#
How to fix the ugliness though? It would have been great if there was no tree and merge here, right? So, basically this happened due to the fact that we are pushing the changes instantly. Let's do that! Pull it down.ĪND, push! The history clarifies what went on behind the scenes. If you read it carefully, you will find that it gives you a hint about pulling from remote and pushing again. Wait, what? An error message? Why did that happen? You can fix this error message, clicking on the Commit button followed by Commit Options > Amend Last Commit option. To demonstrate this case, I have modified the 1.txt file and intentionally introduced a typo in the commit message. You can view the history and if everything is good, you will see the messages along with all the commits.Ĭase 1: How to fix the last commit message? Notice the check box just below the commit message. Click on the Clone option.īy default, with SourceTree you will commit a file and push the changes immediately. You can filter using the search bar to find your repository. Step 1: Setup a repository for testīitbucket and click on the + icon to create a new repository. You can simply follow through, but it would be best if you try it out yourself to get a proper hang of it. This article will try to address various cases where you would want to undo and rewrite history. Recently, I encountered a few folks who were not happy with the easy & traditional undo options in Git. SourceTree to make your Git workflow a lot simpler. If you are not a command-line person, working with Git could be a painful exercise.
0 kommentar(er)
