title: Should I commit Godeps/_workspace or is Godeps.json enough?
body: <p>I'm writing a project in Go to be deployed on heroku, managing dependencies with <a href="https://github.com/tools/godep" rel="nofollow noreferrer">godep</a>.</p>
  
  <p>When I <code>godep save</code>, I get both a <code>Godeps.json</code> file listing my dependencies with versions and an <code>_workspace/</code> directory with the source for all dependencies copied in.  I'd rather not commit <code>_workspace</code>, all that code's already on github elsewhere.  It seems <code>Godeps.json</code> has all the information we need to <code>go get</code> the version locked dependencies at heroku buildpack time.</p>
  
  <p><a href="http://mmcgrana.github.io/2012/09/getting-started-with-go-on-heroku.html" rel="nofollow noreferrer">Several</a> <a href="https://stackoverflow.com/a/24358315/407845">sources</a> recommend committing the full <code>Godeps/</code> directory, but others suggest it <a href="https://github.com/drone/drone/issues/177#issuecomment-37324541" rel="nofollow noreferrer">might not be necessary</a>.</p>
  
  <p>The godep docs aren't much help:</p>
  
  <blockquote>
    <p>This will save a list of dependencies to the file Godeps/Godeps.json, and copy their source code into Godeps/_workspace. Read over its contents and make sure it looks reasonable. Then commit <strong>the file</strong> to version control.</p>
  </blockquote>
  
  <p>Is Godeps.json <strong>the file</strong>?</p>