Remove Gemfile.lock from login-sync 2.0.1
authorPeter Amstutz <peter.amstutz@curii.com>
Tue, 3 Mar 2020 21:17:38 +0000 (16:17 -0500)
committerPeter Amstutz <peter.amstutz@curii.com>
Tue, 3 Mar 2020 21:27:01 +0000 (16:27 -0500)
commit7ad5beea6c92dbb13af52a380a86f8ca1b7e0ff8
tree1049f83aace5511373671e000117740034c72a9a
parent8014ce0457ef848bba8ce18ad5980b9883105cc9
Remove Gemfile.lock from login-sync

no issue #

To be consistent with sdk/ruby sdk/cli behavior.

There's a circular dependency where the version number of the gem is
embedded in Gemfile.lock, but the version number is derived from the
git commit timestamp, so when it updates Gemfile.lock it creates a new
version, which requires a updating Gemfile.lock, and so on.

However, unlike the Ruby on Rails deb/rpm packages, when we create
gems (dev or production) it does not include Gemfile.lock, so there's
no benefit to having it checked in.

Arvados-DCO-1.1-Signed-off-by: Peter Amstutz <peter.amstutz@curii.com>
services/login-sync/.gitignore
services/login-sync/Gemfile.lock [deleted file]