Next, let's use the git switch command to move these uncommitted changes to a new branch called feature2: $ git switch -C feature2 This time, we've removed the file Readme.md and added a new ReadmeNew.md file. Next, let's do the same test as git checkout -b on the myRepo project: $ git branchĪs we can see in the output above, we're currently on the master branch. It works pretty much the same as the git checkout -b command. Moreover, we can use the -C option to create a new branch and switch to it in one shot. As its name implies, git switch allows us to switch between branches. Therefore, Git has introduced the git switch command since version 2.23 to clear some of the confusion from the checkout command's overloaded usage. The usage of the checkout command is pretty overloaded. The same command can do many different kinds of operations, such as restoring the working tree files, switching branches, creating branches, moving the head, and so on. Further, there is no new commit on master, either.Īs we've known, Git's checkout command is like a Swiss Army knife. There is no local change on the master branch, as we can see in the output. Now, let's switch back to the master branch and check if we've left it unchanged: $ git checkout master Next, let's stage and commit the changes: $ git add. No changes added to commit (use "git add" and/or "git commit -a")Īs the commands above show, we've created the feature1 branch and moved all uncommitted changes from master to feature1. " to discard changes in working directory) Next, let's test the git checkout command on our myRepo project: $ git branch Moreover, this command will leave the current branch as it is and bring all uncommitted changes to the new branch. The git checkout -b command will create a new branch and switch to it.
0 Comments
Leave a Reply. |