title: Gitflow with multiple release branches and staging environment
body: <p>So, I've read alot about gitflow.<br>
  One major issue is that it doesn't account for <code>staging</code> environment.<br>
  I can understand that <code>develop</code> branch is mirrored in <code>develop</code> environment and <code>master</code> branch is the <code>production</code> environment.  </p>
  
  <p>Those cases are easy because, there's only one <code>develop</code> branch and one <code>master</code> branch.<br>
  However, a project may have multiple <code>release/v*.*.*</code> branches, but one <code>staging</code> environment.<br>
  Which of the <code>release/</code> branches should I deploy on the <code>staging</code> environment? All? The first one?</p>
  
  <p>How did you handle this issue, considering I don't want to manually decide each time I open a <code>release/</code> if to deploy it to <code>staging</code> or not. I'm looking for a rule of thumb or some other solution I haven't thought of.</p>