diff options
author | Rafael Mendonça França <rafaelmfranca@gmail.com> | 2015-02-18 14:30:25 -0200 |
---|---|---|
committer | Rafael Mendonça França <rafaelmfranca@gmail.com> | 2015-02-18 15:14:46 -0200 |
commit | b1edc3789a39913b889b3ab18039ecca17835df3 (patch) | |
tree | 59bb8407568644842f4faecd2cd0de6167af9d7f /railties/lib/rails/code_statistics_calculator.rb | |
parent | 28fccad2c4ca8159b1c827026cdd09de9c5a3669 (diff) | |
download | rails-b1edc3789a39913b889b3ab18039ecca17835df3.tar.gz rails-b1edc3789a39913b889b3ab18039ecca17835df3.tar.bz2 rails-b1edc3789a39913b889b3ab18039ecca17835df3.zip |
Track Gemfile.lock at the repository
The main reason is to make bisect easier.
In some points, we have a lot of git dependencies. Since we don't have
the information of which commit we are referring to, bundler get the
latest commit of the master branch of the dependency. This sometimes
returns a version that is not compatible with Rails anymore, making the
tests fail and the harder to identify the commit that introduced a bug.
Also this will make sure that a contributor will always get a set of
dependencies that are passing with our tests.
In our CI server we delete the lock file to make sure we are always
testing against the newest release of our dependencies.
Diffstat (limited to 'railties/lib/rails/code_statistics_calculator.rb')
0 files changed, 0 insertions, 0 deletions