Create new branch from master git2/18/2023 ![]() The next step is to delete the master branch on GitHub. Now that we have a main branch on our local computer, a main branch up on GitHub, and the default branch on GitHub is the main branch. Nice job! One more step to get, we just need to get rid of the master branch so that the main branch is the only branch. Next, click the arrows to change the default branchĪfter the default branch change, you can go back to the main repo page and see that main is now the default branch. Then on the lefthand menu, click on branches On the main page for your repo, click on settings. We are going to change it so the default repo and the checkmark are next to the main branch. If you go to the main repo page on GitHub and select the branches dropdown menu, you will see two branches listed and a checkmark next to master. You need to do this on GitHub, not on your local computer. git checkout -b example-tutorial-branch In a text editor like Visual Studio Code, Sublime, vi, or any. You can see which branch you are on using the command below:Ĭhange the default branch on GitHub to main Create a new branch called example-tutorial-branch. The first step is to create a new branch locally (on your computer) called main. Step 1Ĭreate a new main branch locally, taking the history from master Once you’re in the proper directory, you can then create a new branch. So change all of your GitHub repo names to main. This is confusing and leads to creating new branches that you don't want. Is the master branch in charge of anything? Are other branches subservient to it? And a very practical reason is that since GitHub moved to use main as the default branch, you have to remember when to use git push origin main and when to use git push origin master on a repo-to-repo basis. In addition, the name main just makes more sense. Language in programming, like master, that supports symbols of racism has no place. The reason to use the name main as the default branch on Github and in your local git repos is that it's the right thing to do. Moreover, the git log command shows no new commit on master.Git symbolic-ref refs/remotes/origin/HEAD refs/remotes/origin/main For example, the removed file Readme.md has come back. Next, let's switch back to the master branch and check if it's unmodified: $ git switch masterĪs we've seen, on the master branch, all changes to the working tree files we made previously have been restored. Then, we've committed the changes to the feature2 branch. Further, all uncommitted changes have been moved from master to the feature2 branch. & git commit -m 'feature2 is done'ġ file changed, 0 insertions(+), 0 deletions(-)Īs we can see in the output above, git switch -C creates a new branch feature2 and brings us to feature2. 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.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |