Remove Gemfile.lock from login-sync
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:24:38 +0000 (16:24 -0500)
commit5e55bbfce418bbdbd5069a4b6ba14539815e764c
tree8cc19fb8a43594f920bafce1abb225428024acdd
parentaf5e26a900bbfa779ad325491d80f43eaf75de1d
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]