title: Git Forking workflow - integrating feature branch from fork to upstream feature branch
body: <p>From the <a href="https://www.atlassian.com/git/tutorials/comparing-workflows/forking-workflow" rel="nofollow noreferrer">Atlassian documentation</a> on the Forking Workflow, you can read:</p>
  
  <blockquote>
    <p>Second, they need to notify the project maintainer that they want to merge their feature into the official codebase. Bitbucket provides a “pull request” button that leads to a form asking you to specify which branch you want to merge into the official repository. Typically, you’ll want to integrate your feature branch into the upstream remote’s master branch.</p>
  </blockquote>
  
  <p>My question is:</p>
  
  <p>Is it overkill to integrate your <strong>feature branch</strong> into the upstream remote's <strong>feature branch</strong>?</p>
  
  <p>Wouldn't this give you a possibility to add another layer of code review? (maybe within a smaller team)</p>
  
  <p>If not, why?</p>