title: GitHub workflow: Should each developer have their own fork?
body: <p>Our team is using GitHub for the first time. We set it up so that we can use <code>pull requests</code> as a way to do code reviews. </p>
  
  <ol>
  <li>There is a group organization that everyone has rights to, and which contains the canonical repo. </li>
  <li>Each developer <code>forked</code> the group repo and pushes changes to their <code>fork</code>. </li>
  <li>Developers submit a <code>pull request</code> to the group repo when ready, and another developer reviews the code and then <code>pulls</code> it in. </li>
  </ol>
  
  <p>Is this a reasonable work flow? My concern is that the forked repos don't automatically get updated when the group repo gets updated. Would it be better if everyone contributed directly to the group repo? If so, is there a way to use GitHub for convenient code reviews?</p>