bundler 1.15.2 → 1.17.3

data/Rakefile

@@ -1,338 +0,0 @@
-# -*- encoding: utf-8 -*-
-# frozen_string_literal: true
-$:.unshift File.expand_path("../lib", __FILE__)
-require "shellwords"
-require "benchmark"
-
-RUBYGEMS_REPO = if `cd .. && git remote --verbose 2>/dev/null` =~ /rubygems/i
-  File.expand_path("..")
-else
-  File.expand_path("tmp/rubygems")
-end
-
-BUNDLER_SPEC = Gem::Specification.load("bundler.gemspec")
-
-def safe_task(&block)
-  yield
-  true
-rescue
-  false
-end
-
-# Benchmark task execution
-module Rake
-  class Task
-    alias_method :real_invoke, :invoke
-
-    def invoke(*args)
-      time = Benchmark.measure(@name) do
-        real_invoke(*args)
-      end
-      puts "#{@name} ran for #{time}"
-    end
-  end
-end
-
-namespace :spec do
-  desc "Ensure spec dependencies are installed"
-  task :deps do
-    deps = Hash[BUNDLER_SPEC.development_dependencies.map do |d|
-      [d.name, d.requirement.to_s]
-    end]
-    deps["rubocop"] ||= "= 0.48.0" if RUBY_VERSION >= "2.0.0" # can't go in the gemspec because of the ruby version requirement
-
-    # JRuby can't build ronn or rdiscount, so we skip that
-    if defined?(RUBY_ENGINE) && RUBY_ENGINE == "jruby"
-      deps.delete("ronn")
-      deps.delete("rdiscount")
-    end
-
-    gem_install_command = "install --no-ri --no-rdoc --conservative " + deps.sort_by {|name, _| name }.map do |name, version|
-      "'#{name}:#{version}'"
-    end.join(" ")
-    sh %(#{Gem.ruby} -S gem #{gem_install_command})
-
-    # Download and install gems used inside tests
-    $LOAD_PATH.unshift("./spec")
-    require "support/rubygems_ext"
-    Spec::Rubygems.setup
-  end
-
-  namespace :travis do
-    task :deps do
-      # Give the travis user a name so that git won't fatally error
-      system "sudo sed -i 's/1000::/1000:Travis:/g' /etc/passwd"
-      # Strip secure_path so that RVM paths transmit through sudo -E
-      system "sudo sed -i '/secure_path/d' /etc/sudoers"
-      # Install groff so ronn can generate man/help pages
-      sh "sudo apt-get install groff-base -y"
-      # Install graphviz so that the viz specs can run
-      sh "sudo apt-get install graphviz -y 2>&1 | tail -n 2"
-
-      # Install the gems with a consistent version of RubyGems
-      sh "gem update --system 2.6.11"
-
-      $LOAD_PATH.unshift("./spec")
-      require "support/rubygems_ext"
-      Spec::Rubygems::DEPS["codeclimate-test-reporter"] = "~> 0.6.0" if RUBY_VERSION >= "2.2.0"
-
-      # Install the other gem deps, etc
-      Rake::Task["spec:deps"].invoke
-    end
-  end
-end
-
-begin
-  rspec = BUNDLER_SPEC.development_dependencies.find {|d| d.name == "rspec" }
-  gem "rspec", rspec.requirement.to_s
-  require "rspec/core/rake_task"
-
-  desc "Run specs"
-  RSpec::Core::RakeTask.new
-  task :spec => "man:build"
-
-  if RUBY_VERSION >= "2.0.0"
-    # can't go in the gemspec because of the ruby version requirement
-    gem "rubocop", "= 0.48.0"
-    require "rubocop/rake_task"
-    RuboCop::RakeTask.new
-  end
-
-  namespace :spec do
-    task :clean do
-      rm_rf "tmp"
-    end
-
-    desc "Run the real-world spec suite (requires internet)"
-    task :realworld => %w(set_realworld spec)
-
-    task :set_realworld do
-      ENV["BUNDLER_REALWORLD_TESTS"] = "1"
-    end
-
-    desc "Run the spec suite with the sudo tests"
-    task :sudo => %w(set_sudo spec clean_sudo)
-
-    task :set_sudo do
-      ENV["BUNDLER_SUDO_TESTS"] = "1"
-    end
-
-    task :clean_sudo do
-      puts "Cleaning up sudo test files..."
-      system "sudo rm -rf #{File.expand_path("../tmp/sudo_gem_home", __FILE__)}"
-    end
-
-    # Rubygems specs by version
-    namespace :rubygems do
-      rubyopt = ENV["RUBYOPT"]
-      # When editing this list, also edit .travis.yml!
-      branches = %w(master)
-      releases = %w(v1.3.6 v1.3.7 v1.4.2 v1.5.3 v1.6.2 v1.7.2 v1.8.29 v2.0.14 v2.1.11 v2.2.5 v2.4.8 v2.5.2 v2.6.8)
-      (branches + releases).each do |rg|
-        desc "Run specs with Rubygems #{rg}"
-        RSpec::Core::RakeTask.new(rg) do |t|
-          t.rspec_opts = %w(--format progress --color)
-          t.ruby_opts  = %w(-w)
-        end
-
-        # Create tasks like spec:rubygems:v1.8.3:sudo to run the sudo specs
-        namespace rg do
-          task :sudo => ["set_sudo", rg, "clean_sudo"]
-          task :realworld => ["set_realworld", rg]
-        end
-
-        task "clone_rubygems_#{rg}" do
-          unless File.directory?(RUBYGEMS_REPO)
-            system("git clone https://github.com/rubygems/rubygems.git tmp/rubygems")
-          end
-          hash = nil
-
-          if RUBYGEMS_REPO.start_with?(Dir.pwd)
-            Dir.chdir(RUBYGEMS_REPO) do
-              system("git remote update")
-              if rg == "master"
-                system("git checkout origin/master")
-              else
-                system("git checkout #{rg}") || raise("Unknown Rubygems ref #{rg}")
-              end
-              hash = `git rev-parse HEAD`.chomp
-            end
-          elsif rg != "master"
-            raise "need to be running against master with bundler as a submodule"
-          end
-
-          puts "Checked out rubygems '#{rg}' at #{hash}"
-          ENV["RUBYOPT"] = "-I#{File.join(RUBYGEMS_REPO, "lib")} #{rubyopt}"
-          puts "RUBYOPT=#{ENV["RUBYOPT"]}"
-        end
-
-        task rg => ["man:build", "clone_rubygems_#{rg}"]
-        task "rubygems:all" => rg
-      end
-
-      desc "Run specs under a Rubygems checkout (set RG=path)"
-      RSpec::Core::RakeTask.new("co") do |t|
-        t.rspec_opts = %w(--format documentation --color)
-        t.ruby_opts  = %w(-w)
-      end
-
-      task "setup_co" do
-        rg = File.expand_path ENV["RG"]
-        puts "Running specs against Rubygems in #{rg}..."
-        ENV["RUBYOPT"] = "-I#{rg} #{rubyopt}"
-      end
-
-      task "co" => "setup_co"
-      task "rubygems:all" => "co"
-    end
-
-    desc "Run the tests on Travis CI against a rubygem version (using ENV['RGV'])"
-    task :travis do
-      rg = ENV["RGV"] || raise("Rubygems version is required on Travis!")
-
-      if RUBY_VERSION >= "2.0.0"
-        puts "\n\e[1;33m[Travis CI] Running bundler linter\e[m\n\n"
-        Rake::Task["rubocop"].invoke
-      end
-
-      puts "\n\e[1;33m[Travis CI] Running bundler specs against rubygems #{rg}\e[m\n\n"
-      specs = safe_task { Rake::Task["spec:rubygems:#{rg}"].invoke }
-
-      Rake::Task["spec:rubygems:#{rg}"].reenable
-
-      puts "\n\e[1;33m[Travis CI] Running bundler sudo specs against rubygems #{rg}\e[m\n\n"
-      sudos = system("sudo -E rake spec:rubygems:#{rg}:sudo")
-      # clean up by chowning the newly root-owned tmp directory back to the travis user
-      system("sudo chown -R #{ENV["USER"]} #{File.join(File.dirname(__FILE__), "tmp")}")
-
-      Rake::Task["spec:rubygems:#{rg}"].reenable
-
-      puts "\n\e[1;33m[Travis CI] Running bundler real world specs against rubygems #{rg}\e[m\n\n"
-      realworld = safe_task { Rake::Task["spec:rubygems:#{rg}:realworld"].invoke }
-
-      { "specs" => specs, "sudo" => sudos, "realworld" => realworld }.each do |name, passed|
-        if passed
-          puts "\e[0;32m[Travis CI] #{name} passed\e[m"
-        else
-          puts "\e[0;31m[Travis CI] #{name} failed\e[m"
-        end
-      end
-
-      unless specs && sudos && realworld
-        raise "Spec run failed, please review the log for more information"
-      end
-    end
-  end
-
-rescue LoadError
-  task :spec do
-    abort "Run `rake spec:deps` to be able to run the specs"
-  end
-
-  task :rubocop do
-    abort "Run `rake spec:deps` to be able to run rubocop"
-  end
-end
-
-begin
-  require "ronn"
-
-  namespace :man do
-    directory "man"
-
-    sources = Dir["man/*.ronn"].map {|f| File.basename(f, ".ronn") }
-    sources.map do |basename|
-      ronn = "man/#{basename}.ronn"
-      manual_section = ".1" unless basename =~ /.*(\d+)\Z/
-      roff = "man/#{basename}#{manual_section}"
-
-      file roff => ["man", ronn] do
-        sh "#{Gem.ruby} -S ronn --roff --pipe #{ronn} > #{roff}"
-      end
-
-      file "#{roff}.txt" => roff do
-        sh "groff -Wall -mtty-char -mandoc -Tascii #{roff} | col -b > #{roff}.txt"
-      end
-
-      task :build_all_pages => "#{roff}.txt"
-    end
-
-    task :clean do
-      leftovers = Dir["man/*"].reject do |f|
-        File.extname(f) == ".ronn" || f == "man/index.txt"
-      end
-      rm leftovers if leftovers.any?
-    end
-
-    desc "Build the man pages"
-    task :build => ["man:clean", "man:build_all_pages"]
-
-    desc "Remove all built man pages"
-    task :clobber do
-      rm_rf "lib/bundler/man"
-    end
-
-    task(:require) {}
-  end
-
-rescue LoadError
-  namespace :man do
-    task(:require) { abort "Install the ronn gem to be able to release!" }
-    task(:build) { warn "Install the ronn gem to build the help pages" }
-  end
-end
-
-begin
-  require "automatiek"
-
-  Automatiek::RakeTask.new("molinillo") do |lib|
-    lib.download = { :github => "https://github.com/CocoaPods/Molinillo" }
-    lib.namespace = "Molinillo"
-    lib.prefix = "Bundler"
-    lib.vendor_lib = "lib/bundler/vendor/molinillo"
-  end
-
-  Automatiek::RakeTask.new("thor") do |lib|
-    lib.download = { :github => "https://github.com/erikhuda/thor" }
-    lib.namespace = "Thor"
-    lib.prefix = "Bundler"
-    lib.vendor_lib = "lib/bundler/vendor/thor"
-  end
-
-  Automatiek::RakeTask.new("net-http-persistent") do |lib|
-    lib.download = { :github => "https://github.com/drbrain/net-http-persistent" }
-    lib.namespace = "Net::HTTP::Persistent"
-    lib.prefix = "Bundler::Persistent"
-    lib.vendor_lib = "lib/bundler/vendor/net-http-persistent"
-
-    mixin = Module.new do
-      def namespace_files
-        super
-        require_target = vendor_lib.sub(%r{^(.+?/)?lib/}, "") << "/lib"
-        relative_files = files.map {|f| Pathname.new(f).relative_path_from(Pathname.new(vendor_lib) / "lib").sub_ext("").to_s }
-        process_files(/require (['"])(#{Regexp.union(relative_files)})/, "require \\1#{require_target}/\\2")
-      end
-    end
-    lib.send(:extend, mixin)
-  end
-rescue LoadError
-  namespace :vendor do
-    task(:molinillo) { abort "Install the automatiek gem to be able to vendor gems." }
-    task(:thor) { abort "Install the automatiek gem to be able to vendor gems." }
-    task("net-http-persistent") { abort "Install the automatiek gem to be able to vendor gems." }
-  end
-end
-
-desc "Update vendored SSL certs to match the certs vendored by Rubygems"
-task :update_certs => "spec:rubygems:clone_rubygems_master" do
-  require "bundler/ssl_certs/certificate_manager"
-  Bundler::SSLCerts::CertificateManager.update_from!(RUBYGEMS_REPO)
-end
-
-require "bundler/gem_tasks"
-task :build => ["man:build"]
-task :release => ["man:require", "man:build"]
-
-task :default => :spec
-
-Dir["task/*.{rb,rake}"].each(&method(:load))

data/bin/rake

@@ -1,19 +0,0 @@
-#!/usr/bin/env ruby
-# frozen_string_literal: true
-
-load File.expand_path("../with_rubygems", __FILE__) if ENV["RGV"]
-
-require "rubygems"
-
-bundler_spec = Gem::Specification.load(File.expand_path("../../bundler.gemspec", __FILE__))
-bundler_spec.dependencies.each do |dep|
-  begin
-    gem dep.name, dep.requirement
-  rescue Gem::LoadError => e
-    $stderr.puts "#{e.message} (#{e.class})"
-  end
-end
-
-Gem.finish_resolve if Gem.respond_to?(:finish_resolve)
-
-load Gem.bin_path("rake", "rake")

data/bin/rspec

@@ -1,15 +0,0 @@
-#!/usr/bin/env ruby
-# frozen_string_literal: true
-
-load File.expand_path("../with_rubygems", __FILE__) if ENV["RGV"]
-
-require "rubygems"
-
-bundler_spec = Gem::Specification.load(File.expand_path("../../bundler.gemspec", __FILE__))
-bundler_spec.dependencies.each do |dep|
-  gem dep.name, dep.requirement
-end
-
-Gem.finish_resolve if Gem.respond_to?(:finish_resolve)
-
-load Gem.bin_path("rspec-core", "rspec")

data/bin/rubocop

@@ -1,17 +0,0 @@
-#!/usr/bin/env ruby
-# frozen_string_literal: true
-
-load File.expand_path("../with_rubygems", __FILE__) if ENV["RGV"]
-
-require "rubygems"
-
-bundler_spec = Gem::Specification.load(File.expand_path("../../bundler.gemspec", __FILE__))
-bundler_spec.dependencies.each do |dep|
-  gem dep.name, dep.requirement
-end
-
-gem "rubocop", "= 0.48.0"
-
-Gem.finish_resolve if Gem.respond_to?(:finish_resolve)
-
-load Gem.bin_path("rubocop", "rubocop")

data/bin/with_rubygems

@@ -1,39 +0,0 @@
-#!/usr/bin/env ruby
-# frozen_string_literal: true
-
-require "pathname"
-
-def run(*cmd)
-  return if system(*cmd)
-  raise "Running `#{cmd.join(" ")}` failed"
-end
-
-version = ENV.delete("RGV")
-rubygems_path = Pathname.new(__FILE__).join("../../tmp/rubygems").expand_path
-unless rubygems_path.directory?
-  rubygems_path.parent.mkpath unless rubygems_path.directory?
-  run("git", "clone", "https://github.com/rubygems/rubygems.git", rubygems_path.to_s)
-end
-Dir.chdir(rubygems_path) do
-  version = "v#{version}" if version =~ /\A\d/
-  run("git", "checkout", version, "--quiet")
-end if version
-
-rubygems_lib = rubygems_path + "lib"
-ENV["RUBYOPT"] = %(-I#{rubygems_lib} #{ENV["RUBYOPT"]})
-
-if $0 != __FILE__
-  ARGV.unshift($0)
-elsif cmd = ARGV.first
-  possible_dirs = [
-    Pathname.new(__FILE__) + "..",
-    Pathname.new(__FILE__) + "../../exe",
-    rubygems_path + "bin",
-  ]
-  cmd = possible_dirs.map do |dir|
-    dir.join(cmd).expand_path
-  end.find(&:file?)
-  ARGV[0] = cmd.to_s if cmd
-end
-
-exec(*ARGV)

data/doc/README.md

@@ -1,30 +0,0 @@
-# Docs: Contributing and developing Bundler
-
-_If you're looking for documentation on how to use Bundler: visit [bundler.io](http://bundler.io/), or run `bundle help` from the command line. You may also be interested in [troubleshooting common issues](TROUBLESHOOTING.md) found when using Bundler._
-
-Bundler welcomes contributions from *everyone*. While contributing, please follow the project [code of conduct](http://bundler.io/conduct.html), so that everyone can be included.
-
-If you'd like to help make Bundler better, you totally rock! Thanks for helping us make Bundler better.
-
-## Contributing
-
-* [Overview & getting started](contributing/README.md)
-* [How you can help: your first contributions!](contributing/HOW_YOU_CAN_HELP.md)
-* [Bug triage](contributing/BUG_TRIAGE.md)
-* [Getting help](contributing/GETTING_HELP.md)
-* [Filing issues](contributing/ISSUES.md)
-* [Community](contributing/COMMUNITY.md)
-
-## Development
-
-* [Overview](development/README.md)
-* [Development setup](development/SETUP.md)
-* [Submitting pull requests](development/PULL_REQUESTS.md)
-* [Adding new features](development/NEW_FEATURES.md)
-* [Releasing Bundler](development/RELEASING.md)
-
-## Documentation
-
-* [Overview](documentation/README.md)
-* [Writing docs for man pages](documentation/WRITING.md)
-* [Documentation vision](documentation/VISION.md)

data/doc/TROUBLESHOOTING.md

@@ -1,64 +0,0 @@
-# Troubleshooting common issues
-
-Stuck using Bundler? Browse these common issues before [filing a new issue](contributing/ISSUES.md).
-
-## Permission denied when installing bundler
-
-Certain operating systems such as MacOS and Ubuntu have versions of Ruby that require elevated privileges to install gems.
-
-    ERROR:  While executing gem ... (Gem::FilePermissionError)
-      You don't have write permissions for the /Library/Ruby/Gems/2.0.0 directory.
-
-There are multiple ways to solve this issue. You can install bundler with elevated privilges using `sudo` or `su`.
-
-    sudo gem install bundler
-
-If you cannot elevated your privileges or do not want to globally install Bundler, you can use the `--user-install` option.
-
-    gem install bundler --user-install
-
-This will install Bundler into your home directory. Note that you will need to append `~/.gem/ruby/<ruby version>/bin` to your `$PATH` variable to use `bundle`.
-
-## Heroku errors
-
-Please open a ticket with [Heroku](https://www.heroku.com) if you're having trouble deploying. They have a professional support team who can help you resolve Heroku issues far better than the Bundler team can. If the problem that you are having turns out to be a bug in Bundler itself, [Heroku support](https://www.heroku.com/support) can get the exact details to us.
-
-## Other problems
-
-First, figure out exactly what it is that you're trying to do (see [XY Problem](http://xyproblem.info/)). Then, go to the [Bundler documentation website](http://bundler.io) and see if we have instructions on how to do that.
-
-Second, check [the compatibility
-list](http://bundler.io/compatibility.html), and make sure that the version of Bundler that you are using works with the versions of Ruby and Rubygems that you are using. To see your versions:
-
-    # Bundler version
-    bundle -v
-
-    # Ruby version
-    ruby -v
-
-    # Rubygems version
-    gem -v
-
-If these instructions don't work, or you can't find any appropriate instructions, you can try these troubleshooting steps:
-
-    # Remove user-specific gems and git repos
-    rm -rf ~/.bundle/ ~/.gem/bundler/ ~/.gems/cache/bundler/
-
-    # Remove system-wide git repos and git checkouts
-    rm -rf $GEM_HOME/bundler/ $GEM_HOME/cache/bundler/
-
-    # Remove project-specific settings
-    rm -rf .bundle/
-
-    # Remove project-specific cached gems and repos
-    rm -rf vendor/cache/
-
-    # Remove the saved resolve of the Gemfile
-    rm -rf Gemfile.lock
-
-    # Uninstall the rubygems-bundler and open_gem gems
-    rvm gemset use global # if using rvm
-    gem uninstall rubygems-bundler open_gem
-
-    # Try to install one more time
-    bundle install

data/doc/contributing/BUG_TRIAGE.md

@@ -1,36 +0,0 @@
-# Bug triage
-
-Triaging is the work of processing tickets that have been opened by users. Common tasks include verifying bugs, categorizing tickets, and ensuring there's enough information to reproduce the bug for anyone who wants to try to fix it.
-
-We've created an [issues guide](ISSUES.md) to walk users through the process of how to report an issue with the Bundler project. We also have a [troubleshooting guide](../TROUBLESHOOTING.md) to diagnose common problems.
-
-Not every ticket will be a bug in Bundler's code, but open tickets usually mean that the there is something we could improve to help that user. Sometimes that means writing additional documentation or making error messages clearer.
-
-## Triaging existing issues
-
-When you're looking at a ticket, here are the main questions to ask:
-
-  * Can I reproduce this bug myself?
-  * Are the steps to reproduce the bug clearly documented in the ticket?
-  * Which versions of Bundler (1.1.x, 1.2.x, git, etc.) manifest this bug?
-  * Which operating systems (OS X, Windows, Ubuntu, CentOS, etc.) manifest this bug?
-  * Which rubies (MRI, JRuby, Rubinius, etc.) and which versions (1.8.7, 1.9.3, etc.) have this bug?
-
-If you can't reproduce the issue, chances are good that the bug has been fixed already (hurrah!). That's a good time to post to the ticket explaining what you did and how it worked.
-
-If you can reproduce an issue, you're well on your way to fixing it. :)
-
-## Fixing your triaged bug
-
-Everyone is welcome and encouraged to fix any open bug, improve an error message or add documentation. If you have a fix or an improvement to a ticket that you would like to contribute, we have a small guide to help:
-
-  1. Discuss the fix on the existing issue. Coordinating with everyone else saves duplicate work and serves as a great way to get suggestions and ideas if you need any.
-  2. Base your commits on the correct branch. Bugfixes for 1.x versions of Bundler should be based on the matching 1-x-stable branch.
-  3. Review the [pull request guide](../development/PULL_REQUESTS.md).
-  4. Commit the code with at least one test covering your changes to a named branch in your fork.
-  5. Put a line in the [CHANGELOG](../../CHANGELOG.md) summarizing your changes under the next release under the “Bugfixes” heading.
-  6. Send us a [pull request](https://help.github.com/articles/using-pull-requests) from your bugfix branch.
-
-## Duplicates!
-
-Finally, the ticket may be a duplicate of another older ticket. If you notice a ticket is a duplicate, simply comment on the ticket noting the original ticket’s number. For example, you could say “This is a duplicate of issue #42, and can be closed”.

data/doc/contributing/COMMUNITY.md

@@ -1,13 +0,0 @@
-# Community
-
-Community is an important part of all we do. If you’d like to be part of the Bundler community, you can jump right in and start helping make Bundler better for everyone who uses it.
-
-It would be tremendously helpful to have more people answering questions about Bundler (and often simply about [Rubygems](https://github.com/rubygems/rubygems) or Ruby itself) in our [issue tracker](https://github.com/bundler/bundler/issues) or on [Stack Overflow](http://stackoverflow.com/questions/tagged/bundler).
-
-Additional documentation and explanation is always helpful, too. If you have any suggestions for the Bundler website [bundler.io](http://bundler.io), we would absolutely love it if you opened an issue or pull request on the [bundler-site](https://github.com/bundler/bundler-site) repository.
-
-Sharing your experiences and discoveries by writing them up is a valuable way to help others who have similar problems or experiences in the future. You can write a blog post, create an example and commit it to GitHub, take screenshots, or make videos.
-
-Publishing examples of how Bundler is used helps everyone, and we’ve discovered that people already use it in ways that we never imagined when we were writing it. If you’re still not sure what to write about, there are also several projects doing interesting things based on Bundler. They could probably use publicity too.
-
-Finally, all contributors to the Bundler project must agree to the contributor [code of conduct](http://bundler.io/conduct.html). By participating in this project you agree to abide by its terms.

data/doc/contributing/GETTING_HELP.md

@@ -1,11 +0,0 @@
-# Getting help
-
-If you have any questions after reading the documentation for contributing, please feel free to contact either [@indirect](https://github.com/indirect), [@segiddins](https://github.com/segiddins), or [@RochesterinNYC](https://github.com/RochesterinNYC). They are all happy to provide help working through your first bug fix or thinking through the problem you’re trying to resolve.
-
-The best ways to get in touch are:
-
-* [Bundler Slack](https://bundler.slack.com).
-  * Not a member of the Slack? Join the Bundler team slack [here](http://slack.bundler.io/)!
-* [Bundler mailing list](http://groups.google.com/group/ruby-bundler)
-
-You may also find our guide on [filing issues](ISSUES.md) to be helpful as well!

data/doc/contributing/HOW_YOU_CAN_HELP.md

@@ -1,27 +0,0 @@
-# How you can help: your first commits!
-
-If you’re interested in contributing to Bundler, that’s awesome! We’d love your help.
-
-If at any point you get stuck, here's how to [get in touch with the Bundler team for help](GETTING_HELP.md).
-
-## First contribution suggestions
-
-We track [small bugs and features](https://github.com/bundler/bundler/labels/contribution%3A%20small) so that anyone who wants to help can start with something that's not too overwhelming.
-
-Generally, great ways to get started helping out with Bundler are:
-
-  - using prerelease versions (run `gem install bundler --pre`)
-  - [reporting bugs you encounter or suggesting new features](https://github.com/bundler/bundler/issues/new)
-    - see our [issues guide](ISSUES.md) for help on filing issues
-    - see the [new features documentation](../development/NEW_FEATURES.md) for more
-  - adding to or editing [the Bundler documentation website](http://bundler.io) and [Bundler man pages](http://bundler.io/man/bundle.1.html)
-  - [checking issues for completeness](BUG_TRIAGE.md)
-  - closing issues that are not complete
-  - adding a failing test for reproducible [reported bugs](https://github.com/bundler/bundler/issues)
-  - reviewing [pull requests](https://github.com/bundler/bundler/pulls) and suggesting improvements
-  - improving existing code, including suggestions from [PullReview](https://www.pullreview.com/github/bundler/bundler/reviews/master) or [CodeClimate](https://codeclimate.com/github/bundler/bundler)
-  - writing code (no patch is too small! fix typos or bad whitespace)
-    - get started setting up your dev environment with [these instructions](../development/DEVELOPMENT_SETUP.md)
-  - backfilling [unit tests](https://github.com/bundler/bundler/tree/master/spec/bundler) for modules that lack [coverage](https://codeclimate.com/github/bundler/bundler/coverage)
-
-If nothing on those lists looks good, [talk to us](http://slack.bundler.io/), and we'll figure out what you can help with. We can absolutely use your help, no matter what level of programming skill you have at the moment.

data/doc/contributing/ISSUES.md

@@ -1,51 +0,0 @@
-# Filing Issues: a guide
-
-So! You're having problems with Bundler. This file is here to help. If you're running into an error, try reading the rest of this file for help. If you can't figure out how to solve your problem, there are also instructions on how to report a bug.
-
-Before filing an issue, check our [troubleshooting guide](../TROUBLESHOOTING.md) for quick fixes to common issues.
-
-## Documentation
-
-Instructions for common Bundler uses can be found on the [Bundler documentation site](http://bundler.io/).
-
-Detailed information about each Bundler command, including help with common problems, can be found in the [Bundler man pages](http://bundler.io/man/bundle.1.html) or [Bundler Command Line Reference](http://bundler.io/v1.11/commands.html).
-
-## Reporting unresolved problems
-
-Check our [troubleshooting common issues guide](../TROUBLESHOOTING.md) and see if your issues is resolved using the steps provided.
-
-Hopefully the troubleshooting steps above resolved your problem! If things still aren't working the way you expect them to, please let us know so that we can diagnose and hopefully fix the problem you're having.
-
-**The best way to report a bug is by providing a reproduction script.** See these examples:
-
-* [Git environment variables causing install to fail.](https://gist.github.com/xaviershay/6207550)
-* [Multiple gems in a repository cannot be updated independently.](https://gist.github.com/xaviershay/6295889)
-
-A half working script with comments for the parts you were unable to automate is still appreciated.
-
-If you are unable to do that, please include the following information in your report:
-
- - What you're trying to accomplish
- - The command you ran
- - What you expected to happen
- - What actually happened
- - The exception backtrace(s), if any
- - Everything output by running `bundle env`
-
-If your version of Bundler does not have the `bundle env` command, then please include:
-
- - Your `Gemfile`
- - Your `Gemfile.lock`
- - Your Bundler configuration settings (run `bundle config`)
- - What version of bundler you are using (run `bundle -v`)
- - What version of Ruby you are using (run `ruby -v`)
- - What version of Rubygems you are using (run `gem -v`)
- - Whether you are using RVM, and if so what version (run `rvm -v`)
- - Whether you have the `rubygems-bundler` gem, which can break gem executables (run `gem list rubygems-bundler`)
- - Whether you have the `open_gem` gem, which can cause rake activation conflicts (run `gem list open_gem`)
-
-If you have either `rubygems-bundler` or `open_gem` installed, please try removing them and then following the troubleshooting steps above before opening a new ticket.
-
-[Create a gist](https://gist.github.com) containing all of that information, then visit the [Bundler issue tracker](https://github.com/bundler/bundler/issues) and [create a ticket](https://github.com/bundler/bundler/issues/new) describing your problem and linking to your gist.
-
-Thanks for reporting issues and helping make Bundler better!