title: How to maintain base code in separate Git repository?
body: <p>Firstly, I'm new to VSTS and Git, so apologies if my terminology gets muddled!</p>
  
  <h3>PROBLEM</h3>
  
  <p>My situation is that I have a VS/C# Project (called "PluginBase") that is, essentially, "starting template" code for a plugin.  Historically, I've would just copy that PluginBase project code every time I wanted to create a new "tailored/derived" build for a particular customer.</p>
  
  <p>What I would like to be able to do is, as and when bug fixes are resolved and features are added to the PluginBase project, I'd like the option to migrate these changes to one or more of the "tailored/derived" builds.  Likewise, if the bug was first found while developing a "tailored/derived" build, I'd like to migrate that back to the PluginBase plugin.</p>
  
  <h3>IDEAS</h3>
  
  <p>From my research, I've come across a few "possible" ways of achieving my goal, but I'm not sure which (if any) of these approaches are suitable.</p>
  
  <ul>
  <li><strong>Branches</strong>
  
  <ul>
  <li>Seems the common approach, perhaps the "best", but...</li>
  <li>Means all code must be in the same repository? (otherwise can't "cherry pick" across) - which I'd prefer to avoid as this may not always be possible</li>
  </ul></li>
  <li><strong>Git Submodules</strong>
  
  <ul>
  <li>Seems more intended when projects are sharing a common "library" (not deriving from same code-base)</li>
  <li>Also not sure Visual Studio fully supports this feature</li>
  </ul></li>
  <li><strong>Cherry Pick</strong>
  
  <ul>
  <li>Doesn't seem possible to do this from one repository to another?</li>
  </ul></li>
  <li><strong>Git Patch</strong>
  
  <ul>
  <li>Doesn't seem Visual Studio supports this feature yet?</li>
  </ul></li>
  </ul>
  
  <p>So, if anyone has any advice, guidance or new suggestions for approaches I could (or should) be using, I'd really appreciate your input.</p>
  
  <p>Many thanks! :)</p>