title: Avoid merging master into development branch
body: <p>I have been monitoring two branches starting from each sprint - <code>Release</code> and <code>Master</code>. </p>
  
  <p><code>Master</code> branch is from where developers create new branch(task specific), implement their changes, and creates pull request which gets merged into the <code>Master</code>. </p>
  
  <p><code>Release</code> branch is sprint specific which remains always submittable to the production. We only merge branches committed to the <code>Master</code> and verified by the QA into <code>Release</code> branch. </p>
  
  <p>This approach works best for us as we submit <code>Release</code> at fix regular interval with specific functionality implemented and verified, and hence we exactly know what's going in the next release.</p>
  
  <p>It's going great until I ran into following issue;</p>
  
  <ol>
  <li>DeveloperA has created task specific branch say <code>taskA</code> from <code>Master</code>.</li>
  <li>He has committed multiple times to <code>taskA</code> branch.</li>
  <li>Mean while other developerB created his branch <code>taskB</code> from <code>Master</code> and committed multiple changes to the <code>taskB</code> and got <code>taskB</code> merged into <code>Master</code>.</li>
  <li>DeveloperA will merge <code>Master</code> into <code>taskA</code> branch and further carry on his task, and commits more changes into <code>taskA</code> branch!</li>
  <li>Eventually he will get <code>taskA</code> branch merged into <code>Master</code>.</li>
  </ol>
  
  <p>Now I just want to merge <code>taskA</code> branch to <code>Release</code> branch but as <code>taskB</code> was also merged into <code>taskA</code> branch as DeveloperA merged <code>Master</code> into his branch in step#4, I get <code>taskB</code> branch changes automatically into <code>Release</code> branch! I don't want that. </p>
  
  <p>What is the best way to avoid merging <code>Master</code> into <code>Developer</code> branch and what could be the right approach to follow in my case? </p>