What to do with branch after merge

I had two branches: master and branch1. I just merged branch1 back into master and I’m done with that branch. Should I delete it or just let it sit around? Will deleting it cause any loss of data?

  • How do I rename my git 'master' branch to 'release'?
  • git find all unmerged commits in master grouped by the branches they were created in
  • “git branch --track” vs “git checkout --track”
  • Use 'pull' or 'merge' to merge local branches?
  • git shallow clone (clone --depth) misses remote branches
  • How to Determine the Work Items Fixed in a particular TFS Build when using Branches?
  • VCS Migration to Git - How is my approach?
  • git bash: error: RPC failed; result = 18, HTP code = 200B | 1KiB/s
  • PHPStorm, Vendor and multiple Git roots
  • What does MM stand for in git show --raw output for merge commits?
  • Cannot push to github with Powershell
  • Does any version control system have a “persistent local only change” feature?
  • 2 Solutions collect form web for “What to do with branch after merge”

    After the merge, it’s safe to delete the branch:

    git branch -d branch1

    Additionally, git will warn you (and refuse to delete the branch) if it thinks you didn’t fully merge it yet. If you forcefully delete a branch (with git branch -D) which is not completely merged yet, you have to do some tricks to get the unmerged commits back though (see below).

    There are some reasons to keep a branch around though. For example, if it’s a feature branch, you may want to be able to do bugfixes on that feature still inside that branch.

    If you also want to delete the branch on a remote host, you can do:

    git push origin :branch1

    This will forcefully delete the branch on the remote (this will not affect already checked-out repositiories though and won’t prevent anyone with push access to re-push/create it).

    git reflog shows the recently checked out revisions. Any branch you’ve had checked out in the recent repository history will also show up there. Aside from that, git fsck will be the tool of choice at any case of commit-loss in git.

    All my branches are named in the form of Fix/fix- or Ftr/ftr- etc. Using Tower as my git front end, it neatly organizes all the Ftr/, Fix/, Test/ etc. into folders. Once I am done with a branch, I rename them to Done/…- That way the are still there (which can be handy to provide history) and I can always go back knowing what it was (feature, fix, test etc.)

    Git Baby is a git and github fan, let's start git clone.