There are a few ways to accomplish that: Change your local branch and then push your changes Push the branch to remote with the new name while keeping the original name locally Renaming local and remote # Rename the local branch to the new name git branch -m <old_name> <new_name> # Delete the old branch … Read more
Git v2.37.1 and above If you are using the mentioned version or above you can use this new config entry to automatically setup remote tracking: git config –global push.autoSetupRemote true After that, when you do git push tracking is setup automatically. No need for git push -u origin my_branch A shortcut, which doesn’t depend on … Read more
This article advises to instead of merging two branches, you would rebase them where git would only rebase non duplicate commits. But instead of cherry-picking, you might consider just rebasing the branch: rebase –onto release B bug where release is the release branch and bug is the bug branch. You then get something like C’—D’ … Read more
Christopher is right, tagging will help you do this. I recommend deleting the branch name too to make it a little harder for someone to checkout the branch and make edits. First, merge the branch into develop git checkout develop git merge –no-ff feature_1 Then checkout the branch git checkout feature_1 Then create a tag, … Read more
Given that Git uses a directed acyclic graph and usually a repo only has one root, all your branches point back to one initial commit. So what you actually want is the branch that shares the largest part of its history with your branch. You cannot just look for a branch whose HEAD is contained … Read more
Following the FAQ article “How to Rename the master branch to main in Git”, and the GitHub documentation itself, you can: rename your local branch from master to main: git branch -m master main push to main: git push -u origin main update your default branch on GitHub side: Then delete the remote master branch: … Read more
Read e.g. this explanation http://git-scm.com/book/en/Git-Branching-Remote-Branches First let’s clarify some git terminology: fetch: getting contents (or updates) from a remote repo pull: fetch (as above) and merge in one step The original poster did not mention merging, so I might guess in proper git terminology he might even have wanted to ask “git fetch all branches … Read more
As pointed out in the comments and in Jackub’s answer, as long as your branch is younger than the number of days set in the config setting gc.reflogexpire (the default is 90 days), then you can utilize your reflog to find out when a branch reference was first created. Note that git reflog can take … Read more
Branches are stored as files containing the SHA they point to. Try deleting the file for this branch, named localbranch, from the .git/refs/head/ directory within your project: rm .git/refs/heads/localbranch
If not yet committed anywhere (git status shows a bunch of stuff modified, it’s OK if it’s “git add”-ed too): $ git checkout -b newbranch Despite the name checkout this usage (with -b) does not check anything out. The -b flag says “create a new branch”, so git creates the branch-name and makes it correspond … Read more