This project is archived and is in readonly mode.
Ignoring Gemfile.lock
Reported by Łukasz Strzałkowski | March 10th, 2010 @ 07:49 PM | in 3.0.2
Really simple think. In autogenerated .gitignore file there is line with ".bundle". If we ignore "bundle noise" out of box I think we can also add Gemfile.lock to ignores.
Comments and changes to this ticket
-
Yehuda Katz (wycats) March 27th, 2010 @ 09:30 AM
- Milestone cleared.
- State changed from “new” to “invalid”
As per the bundler README, Gemfile.lock should be included in version control.
-
ronin-45124 (at lighthouseapp) July 28th, 2010 @ 11:07 AM
- Importance changed from “” to “Low”
hm sure? from my point of view i thought the lock file represent also the current environment. i use diffrent database gems in development (sqlite) and production (pg). the "problem" is that bundler does ignore the current environment and i have to use 'bundle install --without=production' on my development environment and get a lock file. but on production i will have a diffrent lock file (without sqlite, but with pg)
either i havent understand bundler or check in the lock file is a bad idea...
-
-
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
<h2 style="font-size: 14px">Tickets have moved to Github</h2>
The new ticket tracker is available at <a href="https://github.com/rails/rails/issues">https://github.com/rails/rails/issues</a>
Anil Wadghule
Yehuda Katz (wycats)
Łukasz Strzałkowski