Permalink
Switch branches/tags
Commits on Feb 13, 2018
  1. Tweak language, remove lock info from Gemfile doc.

    indirect committed Feb 13, 2018
    After reviewing, I think the question and answer is a bad fit for the
    `gemfile` man page. It does seem like a good fit for the FAQ page on the
    Bundler documentation site, though, and I'll add it over there.
Commits on Feb 8, 2018
  1. Provide the team-wide email address for contact.

    indirect committed Feb 8, 2018
Commits on Feb 1, 2018
  1. Remove vestigial CONTRIBUTING doc.

    indirect committed Feb 1, 2018
    The primary contributing doc is now located at docs/README.md, and we
    link to that file from the main project README. I think this file causes
    more confusion than it helps with, and anyone interested in contributing
    can get better info from the "Contributing" section in the readme.
  2. Add enforcement steps and examples to the CoC.

    indirect committed Feb 1, 2018
    package.community has done a terrific job with their clear explanation
    of what enforcing a CoC looks like. Bundler is a better place when
    everyone knows what kind of behavior is expected, and what will happen
    if those expectations are not met, for whatever reason.
Commits on Nov 29, 2017
  1. finally working test for the inline double-check

    indirect committed Nov 29, 2017
    this test appears to only fail when the server is rubygems.org, so I
    moved the test into realworld and pulled in vcr.
Commits on Nov 27, 2017
  1. Stop overriding specs during double-checks

    indirect committed Nov 27, 2017
    This fixes my test-case reproduction of #6072. I’m pretty sure it’s
    because the double-check was overriding the locally installed index
    specs with specs fetched from the RubyGems API, causing Bundler to
    conclude that the gems aren’t installed, even though they are.
Commits on Nov 8, 2017
  1. Stop requesting changelogs in PRs

    indirect committed Nov 8, 2017
    We added this requirement before the changelog was automated. Now that the changelog generated by a script, it's not helpful for PRs to update the changelog anymore, so we shouldn't expect it anymore.
Commits on Sep 13, 2017
  1. Expand `env` output

    indirect authored and segiddins committed Sep 7, 2017
Commits on Aug 7, 2017
  1. Extract override version for use installing in dev

    indirect committed Aug 7, 2017
Commits on Jul 21, 2017
  1. collapse examples where possible

    indirect committed Jul 21, 2017
Commits on Mar 31, 2017
  1. github strips css, never mind

    indirect committed Mar 31, 2017
Commits on Mar 2, 2017
Commits on Feb 28, 2017
Commits on Feb 19, 2017
  1. wrap at 80 chars

    indirect committed Feb 19, 2017
Commits on Feb 17, 2017
  1. update wording

    indirect committed Feb 17, 2017
Commits on Feb 16, 2017
  1. remove post-install on account of confusion

    indirect committed Feb 16, 2017
    as demonstrated on twitter[1], this message was unfortunately convincing people that Ruby Together pays for the rubygems.org servers. let's remove it and come up with something clearer later.
    
    [1]: https://twitter.com/MelissaKaulfuss/status/829504864229023744
Commits on Feb 1, 2017
  1. add improving

    indirect committed Feb 1, 2017
Commits on Jan 10, 2017
  1. update link, appeal to better natures

    indirect committed Jan 10, 2017
Commits on Jan 7, 2017
  1. break lines

    indirect committed Jan 7, 2017
  2. Call out the costs and ask profitable Rubyists to give back

    indirect committed Jan 7, 2017
Commits on Dec 9, 2016
  1. Merge pull request #5236 from smlx/patch-1

    indirect committed Dec 9, 2016
    Fix typo in man page.
Commits on Oct 14, 2016
  1. Merge tag 'v1.13.4'

    indirect committed Oct 14, 2016
    Version 1.13.4
  2. add a failing spec for not-found gems

    indirect committed Oct 14, 2016
    This is a kind of weird and specific situation:
    
    If, and only if, some version of a gem is installed into system gems
    (e.g. rack 1.0), then trying to resolve a different version of that gem
    from a specific remote source (e.g. rack 2.0.1.1.forked) will fail, even
    though that gem is in fact available from that soure. Uninstalling the
    unrelated version of rack from system gems completely solves this
    problem. Alternately, running `bundle update rack` instead of `bundle
    install` also completely solves this problem.
    
    From this I speculate that we are unfairly withholding the rack
    2.0.1.1.forked spec from the resolver, even though it was provided by
    the source.
  3. ruby 1.8 can't even give exit statuses

    indirect committed Oct 14, 2016
    how did this ever pass even once 😲
Commits on Oct 13, 2016
  1. holy crap, what a subtle bug

    indirect committed Oct 13, 2016
    THANK YOU RSPEC BISECT
    also THANK YOU @SAMPHIPPEN
    
    So it turns out that the realworld specs make real life network requests
    to the real life rubygems.org. But we have some other “realworld” tests
    that spin up a webrick server to recreate specific pathological server
    behaviors. And those webrick servers might be able to answer requests
    from later realworld tests that are expecting the actual rubygems.org,
    but instead are getting our fake gem server because Artifice was never
    stopped. :O
  2. correct PR number, ht @chrismo

    indirect committed Oct 13, 2016