title: how to cut wrong commit [git]
body: <p>I'm trying to apply gitflow approach in our development process, theoretically I like it. But there is one point what is not covered anywhere...</p>
  
  <p>Everyone pushing their results to <code>develop</code> branch. In plan, we have 10 issues which should be done and released to beta and then to production. 2 from 10 issues are not finally fixed, but partially it is already in develop branch, because developer thought he did it well, but after tests bugs are come again. And now decision we need not to wait while that 2 issues will be fixed and we need to make an upload, means make <code>release</code> branch and test it on beta.</p>
  
  <p>In original gitflow article says:</p>
  
  <blockquote>
    <p>The key moment to branch off a new release branch from develop is when
    develop (almost) reflects the desired state of the new release. At
    least all features that are targeted for the release-to-be-built must
    be merged in to develop at this point in time</p>
  </blockquote>
  
  <p>But what to do if in <code>develop</code> branch history we can see couple not required merges ? Do I need cut them somehow ? or do anything else ?</p>
  
  <p>Thanks. </p>