![what is git bash here what is git bash here](https://gitforwindows.org/img/gwindows_logo.png)
A bit like having two Marty’s in the same timeline - confusing!Īs with Back to the Future, there is always a way out of any problem that may surface. Moreover the history will show the commit twice, albeit with different ids. Git will see that the commit exists twice - the first version and the Rebased version - and potentially get confused when you try to merge the changes together. This means you’d ‘pull the rug from under the feet’ of anyone using the ‘old’ commit. As such a new commit will be created for every step of the process. Remember that Rebase has to follow the rules of a commit - that it is immutable.
#What is git bash here series
Combine a series of commits into one commit.Remove a commit from the history of a change set (or branch).Add a commit into the history of a change set (or branch).Remember, even though you can use Rebase for the following (and maybe more) cases, it remains best practice to commit early and often: Prior knowledge of the fundamental concepts of source control is crucial to understanding this post.
![what is git bash here what is git bash here](https://cdn.appuals.com/wp-content/uploads/2020/06/open1.png)
Rebase is the tool that can make the single biggest impact to achieving this. I’ve talked before about how the history of a codebase is as important as the codebase itself.