| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Add `—all` flag to `bundle update`
### What was the end-user problem that led to this PR?
The problem was that some users would think they needed to run `bundle update` instead of `bundle install`, and we want such a (potentially) destructive action to require more explicit user approval.
### Was was your diagnosis of the problem?
My diagnosis was that `bundle update` shouldn't implicitly update _everything_ without an acknowledgement that it will do so.
### What is your fix for the problem, implemented in this PR?
My fix, based on https://github.com/bundler/bundler/pull/2646, it to require `bundle update --all` for the current `bundle update` behavior.
### Why did you choose this fix out of the possible options?
I chose this fix because it was already on 2-0-dev, courtesy of https://github.com/bundler/bundler-features/issues/18.
|
| | | | | | | |
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
And require it on 2+
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
This will avoid spurious deprecation warnings
|
| | | | | | | |
|
| | | | | | | |
|
| | |/ / / /
| |/| | | | |
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
[DSL] Deprecate the github source for 2.0
Closes #5699.
Closes #5698.
@indirect is this what you wanted?
|
| |/ / / / / |
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Fix headers in contributing README
### What was the end-user problem that led to this PR?
Some headers in contributing/README.md aren't displaying properly.
![bundler 2017-06-14 09-02-41](https://user-images.githubusercontent.com/916368/27142561-407a4cde-50e0-11e7-8681-7cff43ff053f.png)
Also, I promised @indirect that I'd start contributing to bundler last night.
### Was was your diagnosis of the problem?
The markdown was missing some spaces.
### What is your fix for the problem, implemented in this PR?
I added some spaces. TADA!
![bundler 2017-06-14 09-08-32](https://user-images.githubusercontent.com/916368/27142790-0e2a73de-50e1-11e7-86bb-a64d7f43449b.png)
### Why did you choose this fix out of the possible options?
Adding spaces seemed like the most reasonable choice to transition from a state of non-spaces to a spaceful state.
|
| |/ / / / / |
|
|\ \ \ \ \ \
| |/ / / / /
|/| | | | |
| | | | | |
| | | | | |
| | | | | | |
[Pristine] Allow passing a list of gems to pristine
In the process of testing this, I discovered and fixed a bug that had pristine git gems not get added files removed.
|
| | | | | | |
|
| | | | | | |
|
|/ / / / / |
|
|\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Add a PR template
Closes #5715.
|
| | | | | | |
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Ensure Bundler.original_env preserves _all_ keys bundler sets
Closes #5700.
Attempts to make sure we properly preserve missing env variables such as `RUBYOPT` across `bundle exec` invocations so that `Bundler.original_env` is accurate
|
| | |_|_|/ /
| |/| | | | |
|
|\ \ \ \ \ \
| |/ / / / /
|/| | | | |
| | | | | |
| | | | | |
| | | | | | |
[Realworld] Use VCR for network requests
Closes #5099
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
RuboCop already includes this check
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
content-length headers
|
| | | | | | |
|
|/ / / / / |
|
|\ \ \ \ \
| |_|_|/ /
|/| | | |
| | | | |
| | | | |
| | | | | |
generate gems.rb in bundle init with feature flag
This PR adds a feature flag to generate a new `gems.rb` with `bundle init`.
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | |_|/
| |/| | |
|
|\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
[Env] Print shebang when it doesnt match Gem.ruby
Closes #5616.
Prints out `Gem.ruby` and the `bundle` binstub shebang when they don't match, which should help us pinpoint when ruby installation shenanigans are the root cause of an issue
|
| | | | | |
|
| | | | | |
|
| | |/ /
| |/| | |
|
|\ \ \ \
| |/ / /
|/| | |
| | | |
| | | |
| | | | |
[Viz] Work correctly when another gem with a graphviz file is present
Closes #5706 by ensuring we always have the correct gem that contains a requirable `graphviz` file loaded (`ruby-graphviz` is the one we test against and suggest installing)
|
| | | | |
|
|\ \ \ \
| |/ / /
|/| | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
[SpecSet] Sort by name in #tsort
Closes #5696
This is required for backwards compatibility, see
issue #5696 for an example. The issue is that previous versions of bundler would have the load path in one (correct) order, and master has them in another (correct) order. So some projects depend on the load path ordering when multiple gems have the same requirable file.
- [x] Test case
|
| | | | |
|
|/ / /
| | |
| | |
| | |
| | | |
This is required for backwards compatibility, see
issue #5696 for an example
|
|\ \ \
| |/ /
|/| |
| | | |
Version 1.15.1
|