title: How do you review changes of MR that depends on other MR being merged?
body: <p>I am starting to work with other developers on a project where I have mostly worked alone up until now.</p>
  <p>Our repo is hosted on GitLab and I am trying to figure out how to setup a simple git workflow for the team.</p>
  <p>We have a <code>master</code> branch with the code that goes to production and I would like team members to work on feature branches that then get merged onto master.</p>
  <p>For now, when one wants to resolve an Issue, it creates a Merge Request with a branch and pushes code to it. When it's ready they ask for review, and if the review passes I merge the feature branch to <code>master</code>. So far, so good.</p>
  <p>The problem I can't solve right now is: if a team member wants to continue working on another issue that depends on a previous issue being merged, how can I review the code of the dependent merge request?</p>
  <p>In this case, we would have a <code>master</code> branch, a <code>issue-1</code> branch based on <code>master</code> and an <code>issue-2</code> branch based on <code>issue-1</code>.</p>
  <p>If the target of both merge requests is <code>master</code>, when reviewing the changes of <code>issue-2</code> I would also have to sift through the changes of <code>issue-1</code>, which I should have already reviewed separately on <code>issue-1</code> merge request.</p>
  <p>Is it possible to keep <code>master</code> as the target branch for both MRs but use <code>issue-1</code> as the base for the diffs of <code>issue-2</code>?</p>
  <p>I know there's a Merge dependency premium feature, but I don't think it solves this particular problem.</p>
  <p>Thank you in advance for your help.</p>