title: Should Gemfile.lock be committed to source control on Windows?
body: <p>Ruby newb here.</p>
  
  <p>I download ruby via rubyinstaller, did <code>gem install rails</code>, resolved a few missing libraries, and finally forked the <a href="http://selfstarter.us/" rel="nofollow noreferrer">ruby project</a> I want to work on.</p>
  
  <p>Before touching anything, I see that my Gemfile.lock is modified:</p>
  
  <pre><code>diff --git a/Gemfile.lock b/Gemfile.lock
  index aefda68..9ebccba 100644
  --- a/Gemfile.lock
  +++ b/Gemfile.lock
  @@ -46,6 +46,7 @@ GEM
       diff-lcs (1.1.3)
       erubis (2.7.0)
       eventmachine (1.0.0)
  +    eventmachine (1.0.0-x86-mingw32)
       execjs (1.4.0)
         multi_json (~&gt; 1.0)
       hike (1.2.1)
  @@ -65,11 +66,17 @@ GEM
       multi_json (1.3.6)
       multi_xml (0.2.2)
       pg (0.14.1)
  +    pg (0.14.1-x86-mingw32)
       polyglot (0.3.3)
  
  ...
  
   PLATFORMS
     ruby
  +  x86-mingw32
  </code></pre>
  
  <p>All the modified lines seem to be Windows related. <a href="https://stackoverflow.com/a/4151540/11236">This answer</a> seems to indicate that I should not gitignore Gemfile.lock (it's already committed to the repo I cloned anyway). <a href="https://stackoverflow.com/a/6811182/11236">This answer</a> implies I might get errors if I do commit &amp; push it to heroku (makes sense, since I don't want my app to depend on Windows-specific files).</p>
  
  <p>So, which is it? How should I fix it? Should I delete Gemfile.lock from my repo?</p>