Be careful when doing that on branches other people are working on. Keep in mind that now you have changed your local commit history, so it might require a force push to remote. You can start over again instead with git rebase -abort in case something goes wrong. Now your history contains new, more granular commits. When you are done with your surgery, invoke git rebase -continue ), producing as many commits as you need. Commit the pieces individually in the usual way ( git commit. This is the step where you create new smaller commits, or in other words where you split the original one. Now all the changes done in that commit are unstaged and need to be committed again. You are now editing commit 85a90cf New rendering engine. Your commit list in the editor should now look like this: pick ddb5c99 Update graphics Find the commit you want to split in the list and change the pick word into edit (or e in short). In the part you will find instructions on what you can do in this page: we need the edit command to manipulate our commit. Pick 527247a Add support for videos - newer commit I've added - older commit and - newer commit in the snippet below to make it clear, you won't find those notes in the editor: pick ddb5c99 Update graphics - older commit Note that it might be confusing at first, since they are displayed in a reverse order, where the older commit is on top. This command will open up your text editor of choice with a list of all the commits starting from (but excluding) the one you passed in. Say for example that this is your history (as shown with git log -oneline): 527247a (HEAD -> master) Add support for videos The first thing to do is to look at your commits history and pick a commit older than the one you want to split. In this quick tutorial I want to show you how to split a commit into multiple parts the easy way. So instead, you will have to create a (temporary) branch first which you can then check out. Similarly, it will also not allow you to check out a tag (since that would also give you a detached HEAD). Maybe you want to move the changes done to b.txt to another commit, in order to make your history clearer. GitKraken (as of version 1.7) does not seem to offer a way to get into a detached HEAD mode, and check out a commit directly. Then, hours and many commits later, you realize that changes done to b.txt should not be part of that commit. At some point you create a commit that include, say, changes to files a.txt, b.txt and c.txt. Imagine you are working with multiple files in a Git-managed project.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |