Bundler: always use latest revision of git branch in Gemfile

I have a Gemfile with a private git repo in the following format:

gem 'magic_beans', :git => "git@git.example.com:magic_beans.git', :branch => 'super_beans'

  • rake release fail (using gem bundler)
  • Developing gems and using them in rails projects with bundler, is there a faster way?
  • Gemfile.lock always has changes not staged for commit
  • How to create interdependent gems with bundler, and use repositories as the source?
  • Should Gemfile.lock be included in .gitignore?
  • How to force the update of a gem with bundler?
  • When I bundle install, the Gemfile.lock locks it to a specific SHA revision.

    Can I get bundler to always check and use the latest SHA commit and/or update the Gemfile.lock? Notice that when I push updates to the super_beans branch I am not modifying the gem version.

    Ideally, every time I run bundle it would check upstream git repo for a newer SHA revision of the branch.

  • Remove submodule repository from Xcode source control
  • Gitflow Release Tagging Model Creates A Dilemma
  • Merge local master branch with remote master branch in Git
  • Simplest command to grab a read-only copy of a git repository?
  • Using git with ssh-agent on Windows
  • Git hook for merge conflicts
  • 3 Solutions collect form web for “Bundler: always use latest revision of git branch in Gemfile”

    This isn’t how bundler works.
    The point is to allow seamless versioning of dependencies.
    (particularly so you know exactly what version of the code is deployed at any given time).

    If want the latest version, you should just run.

    bundle update magic_beans

    This is exactly the same functionality as if you just say

    gem "rails"

    I’d suggest though, if you have a range of specific things you want to update
    then add a custom binary (say an executable file named bundle_update)

    #!/usr/bin/env bash
    bundle install
    bundle update magic_beans

    Then just do a ./bundle_update when you want to update these things.

    You can run bundle update to update all or specific gems to their latest available version, as stated in the docs.

    Would that help?

    After searching through the documents I finally found the magic way to do this:

    bundle update magic_beans --source magic_beans

    That is to update the magic_beans gem only, but not to touch other locked gems. The doc about this is: http://bundler.io/man/bundle-update.1.html

    Git Baby is a git and github fan, let's start git clone.