summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
...
| * | | | | less commas, float the logo leftAndre Arko2017-03-311-2/+3
| | | | | |
| * | | | | re-order it to prioritize users looking for infoAndre Arko2017-03-021-9/+9
| | | | | |
| * | | | | update wording to be even clearerAndre Arko2017-03-021-2/+2
| | | | | |
| * | | | | clearer, more specific wording about sponsorship and contributingAndre Arko2017-02-271-7/+9
| | | | | |
* | | | | | Auto merge of #5722 - bundler:seg-update-all-flag, r=indirectThe Bundler Bot2017-06-159-13/+79
|\ \ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
| * | | | | | Dont test against the expected version deprecationsseg-update-all-flagSamuel Giddins2017-06-141-4/+4
| | | | | | |
| * | | | | | Add `—all` flag to `bundle update`Samuel Giddins2017-06-146-3/+43
| | | | | | | | | | | | | | | | | | | | | | | | | | | | And require it on 2+
| * | | | | | [Install] Avoid re-writing settings when they won’t changeSamuel Giddins2017-06-141-3/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | This will avoid spurious deprecation warnings
| * | | | | | [Settings] Require the local config file before emitting deprecationsSamuel Giddins2017-06-141-1/+3
| | | | | | |
| * | | | | | Fix major deprecation spec to not accidentally cause deprecationsSamuel Giddins2017-06-141-2/+20
| | | | | | |
| * | | | | | Fix matching against no major deprecationsSamuel Giddins2017-06-141-1/+6
| | |/ / / / | |/| | | |
* | | | | | Auto merge of #5705 - bundler:seg-deprecate-github-git-source, r=indirectThe Bundler Bot2017-06-152-29/+52
|\ \ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | [DSL] Deprecate the github source for 2.0 Closes #5699. Closes #5698. @indirect is this what you wanted?
| * | | | | | [DSL] Deprecate the github source for 2.0seg-deprecate-github-git-sourceSamuel Giddins2017-06-142-29/+52
| |/ / / / /
* | | | | | Auto merge of #5723 - slimeate:fix-headers-in-contributing-readme, r=segiddinsThe Bundler Bot2017-06-151-5/+5
|\ \ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
| * | | | | | Fix headers in contributing READMEJack LaBarba2017-06-141-5/+5
| |/ / / / /
* | | | | | Auto merge of #5681 - bundler:seg-pristine-specific-gems, r=colby-swandaleThe Bundler Bot2017-06-153-11/+65
|\ \ \ \ \ \ | |/ / / / / |/| | | | | | | | | | | | | | | | | | | | | | | [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.
| * | | | | [Pristine] Raise when trying to pristine a missing gemseg-pristine-specific-gemsSamuel Giddins2017-06-142-3/+10
| | | | | |
| * | | | | [Pristine] Allow passing a list of gems to pristineSamuel Giddins2017-06-143-3/+39
| | | | | |
| * | | | | [Pristine] Ensure git gems have added files removedSamuel Giddins2017-06-142-8/+19
|/ / / / /
* | | | | Auto merge of #5717 - bundler:seg-pr-template-questions, r=indirectThe Bundler Bot2017-06-141-0/+18
|\ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Add a PR template Closes #5715.
| * | | | | Add a PR templateseg-pr-template-questionsSamuel Giddins2017-06-121-0/+18
| | | | | |
* | | | | | Auto merge of #5701 - bundler:seg-original-env-all-keys, r=indirectThe Bundler Bot2017-06-1410-24/+58
|\ \ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
| * | | | | | Ensure Bundler.original_env preserves _all_ keys bundler setsseg-original-env-all-keysSamuel Giddins2017-06-1310-24/+58
| | |_|_|/ / | |/| | | |
* | | | | | Auto merge of #5220 - bundler:seg-realworld-vcr, r=indirectThe Bundler Bot2017-06-14663-56/+2526
|\ \ \ \ \ \ | |/ / / / / |/| | | | | | | | | | | | | | | | | | | | | | | [Realworld] Use VCR for network requests Closes #5099
| * | | | | Remove the vcr gem from the specs since we rolled our ownseg-realworld-vcrSamuel Giddins2017-06-131-2/+0
| | | | | |
| * | | | | Add cassettes for realworld trampoline specs used on old RGSamuel Giddins2017-06-138-0/+28
| | | | | |
| * | | | | [Rakefile] Allow re-recording all VCR cassettesSamuel Giddins2017-06-132-2/+12
| | | | | |
| * | | | | Ignore vcr cassettes in quality specsSamuel Giddins2017-06-131-3/+3
| | | | | |
| * | | | | Remove quality spec for single quotesSamuel Giddins2017-06-131-23/+0
| | | | | | | | | | | | | | | | | | | | | | | | RuboCop already includes this check
| * | | | | Add VCR cassettes for realworld specsSamuel Giddins2017-06-13646-0/+2284
| | | | | |
| * | | | | Disallow making realworld network requests on CISamuel Giddins2017-06-132-1/+4
| | | | | |
| * | | | | Get the realworld specs running on 1.8.7 againSamuel Giddins2017-06-135-19/+24
| | | | | |
| * | | | | Re-implement VCR to support marshalled responses with incorrect ↵Samuel Giddins2017-06-131-131/+82
| | | | | | | | | | | | | | | | | | | | | | | | content-length headers
| * | | | | Use a single cassette for the realworld specsSamuel Giddins2017-06-133-3/+1
| | | | | |
| * | | | | [Realworld] Use VCR for network requestsSamuel Giddins2017-06-134-16/+232
|/ / / / /
* | | | | Auto merge of #5704 - bundler:colby/init-new-gemfile-format, r=segiddinsThe Bundler Bot2017-06-137-7/+86
|\ \ \ \ \ | |_|_|/ / |/| | | | | | | | | | | | | | | | | | | generate gems.rb in bundle init with feature flag This PR adds a feature flag to generate a new `gems.rb` with `bundle init`.
| * | | | fix the order of the boolean setting keyscolby/init-new-gemfile-formatColby Swandale2017-06-061-2/+2
| | | | |
| * | | | rename feature flag to `init_gems_rb` and PR feedbackColby Swandale2017-06-055-9/+22
| | | | |
| * | | | dont run template gems.rb through eval quality specColby Swandale2017-06-041-0/+1
| | | | |
| * | | | generate gems.rb in bundle init with feature flagColby Swandale2017-06-046-6/+71
| | |_|/ | |/| |
* | | | Auto merge of #5703 - bundler:seg-environment-shebang-mismatch, r=indirectThe Bundler Bot2017-06-121-19/+44
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | [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
| * | | | [Env] Extract table formatting into a methodseg-environment-shebang-mismatchSamuel Giddins2017-06-121-8/+14
| | | | |
| * | | | [Env] Refactor to ensure the environment is always properly alignedSamuel Giddins2017-06-121-23/+34
| | | | |
| * | | | [Env] Print shebang when it doesnt match Gem.rubySamuel Giddins2017-06-121-0/+8
| | |/ / | |/| |
* | | | Auto merge of #5713 - bundler:seg-viz-other-gem, r=indirectThe Bundler Bot2017-06-123-4/+48
|\ \ \ \ | |/ / / |/| | | | | | | | | | | | | | | [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)
| * | | [Viz] Work correctly when another gem with a graphviz file is presentseg-viz-other-gemSamuel Giddins2017-06-123-4/+48
| | | |
* | | | Auto merge of #5707 - bundler:seg-sort-by-name-spec-set, r=indirectThe Bundler Bot2017-06-062-10/+37
|\ \ \ \ | |/ / / |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | [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
| * | | Add a spec for sorting loaded specs by name on the $LOAD_PATHseg-sort-by-name-spec-setSamuel Giddins2017-06-061-9/+35
| | | |
| * | | [SpecSet] Sort by name in #tsortSamuel Giddins2017-06-061-1/+2
|/ / / | | | | | | | | | | | | This is required for backwards compatibility, see issue #5696 for an example
* | | Merge tag 'v1.15.1'Samuel Giddins2017-06-022-1/+10
|\ \ \ | |/ / |/| | | | | Version 1.15.1