title: why should I delete feature branches when merged to master
body: <p>Most of the git workflows I've seen suggest to delete a <code>branch</code> after it's been merged into master. For example, this <a href="http://nvie.com/posts/a-successful-git-branching-model/" rel="noreferrer">gitflow</a> suggests the following:</p>
  
  <pre><code># Incorporating a finished feature on develop 
  $ git checkout develop
  Switched to branch 'develop'
  $ git merge --no-ff myfeature
  Updating ea1b82a..05e9557
  (Summary of changes)
  $ git branch -d myfeature
  Deleted branch myfeature (was 05e9557).
  $ git push origin develop
  </code></pre>
  
  <p>Why should I delete the branch? I'm also curious what to do when later a bug is discovered that was introduced by the feature - should I create the branch with the same name again, fix bug there, merge into master and again delete the branch?</p>