[ARVADOS] created: 1.3.0-2190-g7ad5beea6

[Git user]

        at  7ad5beea6c92dbb13af52a380a86f8ca1b7e0ff8 (commit)


commit 7ad5beea6c92dbb13af52a380a86f8ca1b7e0ff8
Author: Peter Amstutz <peter.amstutz at curii.com>
Date:   Tue Mar 3 16:17:38 2020 -0500

    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 at curii.com>
-----------------------------------------------------------------------


hooks/post-receive
--