Creating and using branches in Git
This article introduces Git branches. We will see how Git branches can help you organize your projects.
Some of the commands we will deal with are git branch
and git checkout
.
git branch
Use commands to create, display, and delete branches
in Git
We use git branch
commands to create, display, and delete branches.
You cannot use this command to switch between different branches.
-
git branch
Shows all branches in your repository. -
git branch <branch name>
Create a new branch in our repository<branch name>
. -
git branch -d <branch name>
Delete the branch<branch name>
. Merge changes before running this command. -
git branch -D <branch name>
Delete a branch without exception. Use this command when you are sure about the decision. -
git branch -m <branch name>
Rename or move a branch.
Let's create a New_Branch
new branch called .
pc@JOHN MINGW64 ~/Git (main)
$ git branch New_Branch
Check if the branch exists.
pc@JOHN MINGW64 ~/Git (main)
$ git branch
New_Branch
* main
We have two branches from the above output, New_Branch
and main
.
Now let's try to delete New_Branch
.
pc@JOHN MINGW64 ~/Git (main)
$ git branch -d New_Branch
Deleted branch New_Branch (was 78129a6).
When you have unmerged changes, you will get an error message. Use to git push origin --delete <branch name>
delete the branch from the remote repository.
git checkout -b <branch>
Create a new branch with the current Git changes
using
git checkout
Commands switch between branches of a project.
To check out an existing branch in a repository, use git checkout <branch>
. Below is an example.
$ git branch
Last_Branch
New_Branch
* main
pc@JOHN MINGW64 ~/Git (main)
$ git checkout New_Branch
Switched to branch 'New_Branch'
M .bash_history
M text.txt.txt
M text.txt.txt.bak
In the code above, we have two branches, New_Branch
and Last_Branch
. We use to switch to git checkout New_Branch
from our branch .main
New_Branch
Use git checkout -b <branch>
to switch to a new branch. Let's look at an example.
pc@JOHN MINGW64 ~/Git (New_Branch)
$ git checkout -b Branch1
Switched to a new branch 'Branch1'
When you switch to a new branch, Git automatically saves your changes from the current branch to the new branch. Take a look at this.
pc@JOHN MINGW64 ~/Git (Branch1)
$ git status
On branch Branch1
Changes not staged for commit:
(use "git add <file>..." to update what will be committed)
(use "git restore <file>..." to discard changes in working directory)
modified: .bash_history
modified: text.txt.txt
modified: text.txt.txt.bak
Untracked files:
(use "git add <file>..." to include in what will be committed)
.bash_history.bak
no changes added to commit (use "git add" and/or "git commit -a")
The above output proves that Git saved the changes from main
branch to Branch1
.
For reprinting, please send an email to 1244347461@qq.com for approval. After obtaining the author's consent, kindly include the source as a link.
Related Articles
Git force pull
Publish Date:2025/03/29 Views:166 Category:Git
-
In this tutorial, we will learn how to force pull changes from a remote repository in Git. Sometimes, we may need to discard local modifications and replace them with updates from a remote repository in a collaborative development environme
Git pulls Master into the branch
Publish Date:2025/03/29 Views:193 Category:Git
-
When developing software using the Git tool, you can create different branches for different features. When you make changes to master, these changes are not automatically added to other branches. This article will explain how to pull all t
Installing Git in Cygwin
Publish Date:2025/03/29 Views:116 Category:Git
-
Git is considered an active, innovative and highly recommended distributed version control system with a fantastic standalone command line while providing us with advanced features and complete internal methods. What is Cygwin Cygwin is con
Displaying remote repository information in Git
Publish Date:2025/03/29 Views:140 Category:Git
-
This tutorial is about displaying information about remote repositories in Git. We use Git, a version control system, to track changes made to files in our project directories through Git repositories. Usually, local repositories are tracke
Deleting a remote repository in Git
Publish Date:2025/03/29 Views:131 Category:Git
-
When we commit the wrong data to the origin, push it to the origin and merge it to the current branch. But later we realize that we don't need to do the merge in that repo, so the question here is how to undo or revert the merge commit that
Setting up a Git remote repository
Publish Date:2025/03/29 Views:78 Category:Git
-
This article will explain how to add or delete remote repositories. A remote repository is a project hosted somewhere, such as Github/Gitlab. Adding a remote repository allows us to use a short name (alias) to execute commands instead of ty
.git Directory Explanation
Publish Date:2025/03/29 Views:66 Category:Git
-
In this article, we'll introduce Git folders .git . We'll cover why Git creates folders and what they contain. .git What are folders in Git ? Git is a widely used version control system. Git repositories store the changes you make in your p
Cherry-Pick Merge Commits in Git
Publish Date:2025/03/29 Views:106 Category:Git
-
When multiple developers from the same team are working on a project, regardless of the complexity of the project, handling and managing changes between Git branches becomes very difficult. Sometimes, we need to merge some specific commits
Fatal: Refusing to Merge Unrelated Histories error in Git
Publish Date:2025/03/29 Views:123 Category:Git
-
This article outlines the steps required to resolve the fatal: refusing to merge unrelated histories error in Git. We usually encounter such errors when trying to merge two unrelated Git projects into one branch. It pops up when the receivi