title: How to work with Git and release via SVN?
body: <p><strong>Is there a way to work completely with Git &amp; GitHub and when it comes time to deploy we (force) merge the latest snapshot to an SVN branch?</strong></p>
  
  <p>Example workflow (repeatable for different branches):</p>
  
  <ol>
  <li>Clone Git repo</li>
  <li>Checkout, branch, make changes, etc.</li>
  <li>Open pull request to <code>master</code></li>
  <li>Merge PR</li>
  <li>Commit to SVN <code>trunk</code></li>
  </ol>
  
  <p>We have experimented with <code>git-svn</code> and <a href="http://www.subgit.com/" rel="nofollow">SubGit</a> but they both seem to obfuscate the process and add complexity.  </p>
  
  <p>For example, <code>git-svn</code> offers <code>dcommit</code> which commits based on deltas, but doesn't seem to allow taking the latest snapshot (without commit history) and force-pushing to SVN.  I suppose we could squash the commit history in another branch, but that's an extra step that we'd like to avoid if possible.</p>
  
  <p>Both products also attempt to synchronize changes from SVN, which we don't ever want to do.  It's a one-way street.</p>
  
  <p>We considered the approach of checking out an SVN repo and simply "adding" a Git repo on top (ignoring <code>.git</code> and <code>.svn</code> respectively) but SVN being folder-based causes problems.  For example, where would the Git repo be <code>init</code>'d in the following structure?</p>
  
  <pre><code>my-project
    |-- trunk/
    |-- branches/
          |-- integration/
          |-- staging/
          |-- uat/
    |-- tags/
  </code></pre>
  
  <p>We do have an automated build/release process, so any potential solution would ideally be implemented there (as opposed to a manual effort).</p>