Should I remove merged branches?

I wanted to start working on ‘feature a’, so I created a new branch git checkout -b feature-a. When the feature was finished and working correctly, I merged it in master git checkout master; git merge feature-a.

The problem is that now git branch still shows ‘feature-a’, which I don’t want beacause I think this will soon become a mess, the list will bee too long.

  • How does git bisect skip choose the next commit to try?
  • EGit marks files as having conflicts but the Merge Tool editor shows no red markers
  • How can I commit specific directory to a different than a working branch on git?
  • Undo multiple file and folder 'git add'
  • build.gradle dependency on gitlab (local server)
  • Azure Web App of nodejs application loads blank screen after deployment
  • Is there a way to remove it from the list? Should I do that?

  • Short syntax for ignoring directory/ and .directory/ in .gitignore?
  • Is git suitable for one developer without server
  • pull instead of fetch - accidentally merged remote master into local branch
  • How can I push my changes to a remote branch
  • Git Error : 'upstream' does not appear to be a git repository
  • Push changes to remote repo without commit
  • One Solution collect form web for “Should I remove merged branches?”

    You can delete the unwanted local branch with git branch -d feature-a

    Preferable to delete unwanted local branches to avoid clutter.

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