Codecov Report

Merging #1475 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #1475   +/-   ##
=======================================
  Coverage   96.97%   96.97%           
=======================================
  Files         492      492           
  Lines        8311     8311           
=======================================
  Hits         8060     8060           
  Misses        251      251

I don't know about this. Don't we risk these files becoming obsolete over time?

Well, yes, just like any other file you keep in version control, right? However, due to their simplicity (they just make sure the correct Gemfile environment is loaded so they can select the right executable) and the super extra care of bundler & rubygems towards backwards compatibility, these files usually have ~0 churn.

IMHO this is a shortcoming of how ruby works, and there's already tools that try to work around this (rbenv, chruby, rvm...).

The fact that we dislike them is just another reason why using bundle exec isn't such a bad idea, even if it's a bit of a PITA.

Note that those are ruby managers, and bundler is a library manager. I don't dislike ruby version managers (I actually use them every day...), but how do you ensure the correct version of a library is loaded using those tools? In my opinion, keeping these files in source control is just a nice convenience at little cost.

Having said all that, I just thought of another way to not need this. I think I can get the same candy by adding an unlikely folder to end up in source control to my global .gitignore file, like deivid-bin/, and put the binstubs in there! So closing!

Some references from rbenv's wiki:

• Binstubs in general.
• Bundler binstubs.