Let’s say you have a website that’s ready for people to see. Usually the first branch we as developers is the development branch. If we run the command to list the branches again, we will see that a new branch is added and that we are located in it. Meanwhile, when this fix came, to add some additional functionalities, it was pulled to a feature branch. Let’s assume you are working on a project along with your friend. You both are working on two different features and hence are working on two different branches.
Moreover, once the branch creates, the whole main code from the main branch gets copied to the newly created branch. Whereas, in Git, the code is separated only from the point of creation of the branch. Once the creation of the new branch happens, we can switch to this branch and start development. Use -r together with -d to delete remote-tracking branches. Note, that it
only makes sense to delete remote-tracking branches if they no longer exist
in the remote repository or if git fetch was configured not to fetch
them again. See also the prune subcommand of git-remote[1] for a

way to clean up all obsolete remote-tracking branches.

What is a branch in Git?

Once you create the development branch, you can see two branches in your branches section—master and development. Once you name your branch, click on create and checkout. Checkout, in this case, means to move to the development branch. Git branches are commonly used when there’s a new feature, bug fix, or anything else in your code you might want to track and compare to previous versions. This helps to identify and track instances where something goes wrong with a bug fix or a new feature release. Knowing how to use development branches becomes vital to develop our application in an orderly way.
Do not rename a branch like master/main/mainline without having read the section Changing the master branch name. Branch description, can be edited with

• Once the delete is done, you can take a look at the Git history.
• As a result, GitHub has automatically retargeted the pull request for feature2 so that its base branch is now main.
• Usually the first branch we as developers is the development branch.
• Now you get the call that there is an issue with the website, and you need to fix it immediately.
• You can switch from master to any other branch available on your repository without making any commit.

git branch –edit-description. Branch description is

Operations on Branches

automatically added in the format-patch cover letter or

request-pull summary. The syntax and
supported options are the same as those of git-merge[1], but
option values containing whitespace characters are currently not
supported. Set up ‘s tracking information so is

Bug Branches

considered ‘s upstream branch. If no
is specified, then it defaults to the current branch.
The local repo is a complete copy of the remote repo. Whenever you propose a change in Git, you create a new branch. Branch management is an important part of the Git workflow. After some time, your list of branches may grow, so it’s a good idea to delete merged or stale branches.
First, we need to commit to the main branch for Git to understand what the master branch is. So first, commit and then create the development branches. Using Git development branches is a pretty great way to work with our application while tracking its versions. In general, a development branch is a bifurcation of the state of code that creates a new path for the evolution of it. It can be parallel to other Git branches that you can generate. As we can see, it is possible to incorporate new functionalities to our code in an orderly and precise way.
Now let’s see just how quick and easy it is to work with different branches, and how well it works. Branches are central to collaboration on GitHub, and the best way to view them is the branches page. If you create a branch on GitHub, you’ll need to publish the branch to make it available for collaboration on GitHub.
Since I have made no-commit before merging, so the output is showing as already up to date. Either we can use git branch – list or git branch command to list the available branches in the repository. When you create a new repository in GitHub, there’s one branch by default—the “main” branch (previously called “master”).

In the meantime, you decide to develop another feature and wait for the client’s approval. Only list branches whose tips are not reachable from the
specified commit (HEAD if not specified). Only list branches whose tips are reachable from the
specified commit (HEAD if not specified). Open an editor and edit the text to explain what the branch is

for, to be used by various other commands (e.g. format-patch,
request-pull, and merge (if enabled)). If no branch

is specified it defaults to the current branch.
When the work is complete, a branch can be merged with the main project. In Git, a branch is a new/separate version of the main repository. You can use GitHub Desktop to create a new branch off of an existing branch in your repository so you can safely experiment with changes. definition of branch By default, GitHub names the default branch main in any new repository. Branches allow you to develop features, fix bugs, or safely experiment with new ideas in a contained area of your repository. This command will delete the existing branch B1 from the repository.