Please don't rebase or amend the master branch about rbenv-bundler HOT 3 CLOSED

@jwhitley Point taken about the automated workflow. I got the impression that most people used the plugin purely for development purposes, and so a little amending wouldn't ruin anyone's day. Out of curiosity, what type of environment is rbenv-bundler included in?

from rbenv-bundler.

Thanks for understanding!

To your question, we're using rbenv-installer to setup rbenv with ruby-build, rbenv-vars, and rbenv-bundler as part of the host-side ruby environment for an automated Vagrant VM setup. There's a top-level toolbox script with an "install/update the universe" command that uses rbenv-installer to update the rbenv plugins, which is where things break down. In this case, the developers using this environment aren't necessarily directly using rbenv at all. The aforementioned top-level toolbox script loads and manages the rbenv environment, so rbenv itself is "under the hood" unless a dev chooses to load it in their rcfiles.

Likewise, I'm already thinking about using this same strategy for maintaining rbenv + bundler inside of a Vagrant VM environment (or other Chef-driven env).

from rbenv-bundler.

Well, I guess rbenv-bundler grew up and the master branch is no longer my "anything goes" playground. The automated pulls underline that fact. FYI, you can still pull from rewritten history: Just add --rebase.

from rbenv-bundler.