diff options
| author | Bundlerbot <bot@bundler.io> | 2019-04-12 01:06:51 +0000 |
|---|---|---|
| committer | Bundlerbot <bot@bundler.io> | 2019-04-12 01:06:51 +0000 |
| commit | abc29c377f24554f7d3101cd5fd081cb1ec33a11 (patch) | |
| tree | 48f92de192405d12cb5de00bc5a43f393a6f1685 /man | |
| parent | 0b5581c911061c6f6bc545f3b91e187333880392 (diff) | |
| parent | eaadb8d8c853fbc7cc04de503eaf447f7ecc6361 (diff) | |
| download | bundler-abc29c377f24554f7d3101cd5fd081cb1ec33a11.tar.gz | |
Merge #7113
7113: Make `init_gems_rb` a regular setting r=indirect a=deivid-rodriguez
### What was the end-user problem that led to this PR?
The problem was that we have a feature flag to change the file name of the file where gems are defined from `Gemfile` to `gems.rb`, and it is unclear whether we will actually do this, and when.
### What was your diagnosis of the problem?
My diagnosis was that a feature flag is not a good fit here. It's perfectly fine to configure this and allow users to use `gems.rb` by default for their gems, but we don't know when/if we will actually change the default so a plain setting feels better than a feature flag.
### What is your fix for the problem, implemented in this PR?
My fix is to convert the `init_gems_rb` feature flag into a plain setting.
Co-authored-by: David RodrÃguez <deivid.rodriguez@riseup.net>
Diffstat (limited to 'man')
0 files changed, 0 insertions, 0 deletions