title: Migrating from SourceGear Vault Source Control to GitHub - Set up
body: <p>I'm looking into migrating our existing ASP.NET projects in SourceGear Vault to Github.</p>
  
  <p>The PROJECTS are PROJ1, PROJ2, PROJ3.
  - where PROJ2 and PROJ3 are forked from the original PROJ1. 
  - All bug fixes done in PROJ1 was always pushed and synchronized to PROJ2 and PROJ3.</p>
  
  <p>The current set up in our existing Source Control is as follows:</p>
  
  <ol>
  <li><p>PROJ1 > Webforms Project which has the BL, DAO, WebApp...etc ( all under the same solution  )</p></li>
  <li><p>PROJ2 > Webforms Project and  was forked from PROJ1 ( at some point in time ~ 1 yr of work and contains mostly Front end UI changes but most back end logic and architecture is still the same ). This is the next Release which will be done within 6 months as BETA </p></li>
  <li><p>PROJ3 > This is an attempt to move away from the conventional WebForms Project to  Angular with WebAPI Architecure... So reusing some of the BL and exposing them as REST Service , and having an Angular Framework Client. This is a version we will be doing may be in 1 - 2 years time.</p></li>
  </ol>
  
  <p>How can I set these up in GitHub so that we can :</p>
  
  <ol>
  <li>Keep pushing bug fixes discovered and fixed in PROJ1 to PROJ2 and PROJ3 ?</li>
  <li>At any point in time, if a dev is assigned to work exlusively in PROJ2 or PROJ3 ( for new features ) OR can switch back to PROJ1 ( for bug fixing)</li>
  </ol>
  
  <p>Ex: Do we create 3 Repository in GitHub? Do we create One Master Repo and Create 2 Branches (PROJ2, PROJ3)...etc How do we handle Merge between PROJECTS ( when a bug is fixed in PROJ1)..</p>
  
  <p>Assumption: We will always fix in 1 and push to 2 and 3 but never backwards.</p>
  
  <p>Any pointers will be greatly appreciated.</p>