bundler 2.1.0 → 2.2.0.rc.1

data/man/bundle-config.ronn

@@ -11,7 +11,7 @@ This command allows you to interact with Bundler's configuration system.
 
 Bundler loads configuration settings in this order:
 
-1. Local config (`app/.bundle/config`)
+1. Local config (`<project_root>/.bundle/config` or `$BUNDLE_APP_CONFIG/config`)
 2. Environmental variables (`ENV`)
 3. Global config (`~/.bundle/config`)
 4. Bundler default config
@@ -30,8 +30,10 @@ overridden and user will be warned.
 
 Executing `bundle config set --global <name> <value>` works the same as above.
 
-Executing `bundle config set --local <name> <value>` will set that configuration to
-the local application. The configuration will be stored in `app/.bundle/config`.
+Executing `bundle config set --local <name> <value>` will set that configuration
+in the directory for the local application. The configuration will be stored in
+`<project_root>/.bundle/config`. If `BUNDLE_APP_CONFIG` is set, the configuration
+will be stored in `$BUNDLE_APP_CONFIG/config`.
 
 Executing `bundle config unset <name>` will delete the configuration in both
 local and global sources.
@@ -179,8 +181,6 @@ learn more about their operation in [bundle install(1)](bundle-install.1.html).
    When set, Gemfiles containing multiple sources will produce errors
    instead of warnings.
    Use `bundle config unset disable_multisource` to unset.
-* `disable_platform_warnings` (`BUNDLE_DISABLE_PLATFORM_WARNINGS`):
-   Disable warnings during bundle install when a dependency is unused on the current platform.
 * `disable_shared_gems` (`BUNDLE_DISABLE_SHARED_GEMS`):
    Stop Bundler from accessing gems installed to RubyGems' normal location.
 * `disable_version_check` (`BUNDLE_DISABLE_VERSION_CHECK`):
@@ -249,9 +249,6 @@ learn more about their operation in [bundle install(1)](bundle-install.1.html).
    be changed in the next major version.
 * `silence_root_warning` (`BUNDLE_SILENCE_ROOT_WARNING`):
    Silence the warning Bundler prints when installing gems as root.
-* `skip_default_git_sources` (`BUNDLE_SKIP_DEFAULT_GIT_SOURCES`):
-   Whether Bundler should skip adding default git source shortcuts to the
-   Gemfile DSL.
 * `specific_platform` (`BUNDLE_SPECIFIC_PLATFORM`):
    Allow bundler to resolve for the specific running platform and store it in
    the lockfile, instead of only using a generic platform.
@@ -396,4 +393,3 @@ outlines the available environment variables and their default values
     BUNDLE_USER_CACHE : $BUNDLE_USER_HOME/cache
     BUNDLE_USER_CONFIG : $BUNDLE_USER_HOME/config
     BUNDLE_USER_PLUGIN : $BUNDLE_USER_HOME/plugin
-

data/man/bundle-doctor.1

@@ -1,7 +1,7 @@
 .\" generated with Ronn/v0.7.3
 .\" http://github.com/rtomayko/ronn/tree/0.7.3
 .
-.TH "BUNDLE\-DOCTOR" "1" "December 2019" "" ""
+.TH "BUNDLE\-DOCTOR" "1" "July 2020" "" ""
 .
 .SH "NAME"
 \fBbundle\-doctor\fR \- Checks the bundle for common problems

data/man/bundle-doctor.1.txt

@@ -1,4 +1,4 @@
-BUNDLE-DOCTOR(1)					      BUNDLE-DOCTOR(1)
+BUNDLE-DOCTOR(1)                                              BUNDLE-DOCTOR(1)
 
 
 
@@ -10,7 +10,7 @@ SYNOPSIS
 
 DESCRIPTION
        Checks  your Gemfile and gem environment for common problems. If issues
-       are detected, Bundler  prints  them  and  exits	status	1.  Otherwise,
+       are detected, Bundler  prints  them  and  exits  status  1.  Otherwise,
        Bundler prints a success message and exits status 0.
 
        Examples of common problems caught by bundle-doctor include:
@@ -29,16 +29,16 @@ DESCRIPTION
 
 OPTIONS
        --quiet
-	      Only output warnings and errors.
+              Only output warnings and errors.
 
        --gemfile=<gemfile>
-	      The  location  of  the Gemfile(5) which Bundler should use. This
-	      defaults to a Gemfile(5) in the current  working	directory.  In
-	      general, Bundler will assume that the location of the Gemfile(5)
-	      is also the project's root and will try to find Gemfile.lock and
-	      vendor/cache relative to this location.
+              The  location  of  the Gemfile(5) which Bundler should use. This
+              defaults to a Gemfile(5) in the current  working  directory.  In
+              general, Bundler will assume that the location of the Gemfile(5)
+              is also the project's root and will try to find Gemfile.lock and
+              vendor/cache relative to this location.
 
 
 
 
-				 December 2019		      BUNDLE-DOCTOR(1)
+                                   July 2020                  BUNDLE-DOCTOR(1)

data/man/bundle-exec.1

@@ -1,7 +1,7 @@
 .\" generated with Ronn/v0.7.3
 .\" http://github.com/rtomayko/ronn/tree/0.7.3
 .
-.TH "BUNDLE\-EXEC" "1" "December 2019" "" ""
+.TH "BUNDLE\-EXEC" "1" "July 2020" "" ""
 .
 .SH "NAME"
 \fBbundle\-exec\fR \- Execute a command in the context of the bundle

data/man/bundle-exec.1.txt

@@ -1,4 +1,4 @@
-BUNDLE-EXEC(1)							BUNDLE-EXEC(1)
+BUNDLE-EXEC(1)                                                  BUNDLE-EXEC(1)
 
 
 
@@ -9,47 +9,48 @@ SYNOPSIS
        bundle exec [--keep-file-descriptors] command
 
 DESCRIPTION
-       This  command  executes	the  command, making all gems specified in the
+       This  command  executes  the  command, making all gems specified in the
        [Gemfile(5)][Gemfile(5)] available to require in Ruby programs.
 
-       Essentially, if you  would  normally  have  run	something  like  rspec
-       spec/my_spec.rb,  and  you  want to use the gems specified in the [Gem-
-       file(5)][Gemfile(5)]  and  installed   via   bundle   install(1)   bun-
-       dle-install.1.html, you should run bundle exec rspec spec/my_spec.rb.
+       Essentially, if you  would  normally  have  run  something  like  rspec
+       spec/my_spec.rb,  and  you  want  to  use  the  gems  specified  in the
+       [Gemfile(5)][Gemfile(5)]   and   installed   via   bundle    install(1)
+       bundle-install.1.html,    you    should    run    bundle   exec   rspec
+       spec/my_spec.rb.
 
-       Note  that bundle exec does not require that an executable is available
+       Note that bundle exec does not require that an executable is  available
        on your shell's $PATH.
 
 OPTIONS
        --keep-file-descriptors
-	      Exec in Ruby 2.0 began discarding non-standard file descriptors.
-	      When  this flag is passed, exec will revert to the 1.9 behaviour
-	      of passing all file descriptors to the new process.
+              Exec in Ruby 2.0 began discarding non-standard file descriptors.
+              When this flag is passed, exec will revert to the 1.9  behaviour
+              of passing all file descriptors to the new process.
 
 BUNDLE INSTALL --BINSTUBS
-       If  you	use  the   --binstubs	flag   in   bundle   install(1)   bun-
-       dle-install.1.html,  Bundler  will  automatically  create  a  directory
-       (which defaults to app_root/bin)  containing  all  of  the  executables
+       If    you    use    the    --binstubs   flag   in   bundle   install(1)
+       bundle-install.1.html, Bundler will automatically  create  a  directory
+       (which  defaults  to  app_root/bin)  containing  all of the executables
        available from gems in the bundle.
 
-       After  using --binstubs, bin/rspec spec/my_spec.rb is identical to bun-
-       dle exec rspec spec/my_spec.rb.
+       After using  --binstubs,  bin/rspec  spec/my_spec.rb  is  identical  to
+       bundle exec rspec spec/my_spec.rb.
 
 ENVIRONMENT MODIFICATIONS
-       bundle exec makes a number of changes to the  shell  environment,  then
+       bundle  exec  makes  a number of changes to the shell environment, then
        executes the command you specify in full.
 
-       o   make  sure  that  it's  still  possible to shell out to bundle from
-	   inside a command invoked by bundle exec (using $BUNDLE_BIN_PATH)
+       o   make sure that it's still possible to  shell  out  to  bundle  from
+           inside a command invoked by bundle exec (using $BUNDLE_BIN_PATH)
 
-       o   put	the  directory	containing  executables  (like	rails,	rspec,
-	   rackup) for your bundle on $PATH
+       o   put  the  directory  containing  executables  (like  rails,  rspec,
+           rackup) for your bundle on $PATH
 
-       o   make  sure  that if bundler is invoked in the subshell, it uses the
-	   same Gemfile (by setting BUNDLE_GEMFILE)
+       o   make sure that if bundler is invoked in the subshell, it  uses  the
+           same Gemfile (by setting BUNDLE_GEMFILE)
 
-       o   add -rbundler/setup to $RUBYOPT, which makes sure  that  Ruby  pro-
-	   grams invoked in the subshell can see the gems in the bundle
+       o   add  -rbundler/setup  to  $RUBYOPT,  which  makes  sure  that  Ruby
+           programs invoked in the subshell can see the gems in the bundle
 
 
 
@@ -57,122 +58,124 @@ ENVIRONMENT MODIFICATIONS
 
        o   disallow loading additional gems not in the bundle
 
-       o   modify  the gem method to be a no-op if a gem matching the require-
-	   ments is in the bundle, and to raise a Gem::LoadError if it's not
+       o   modify the gem  method  to  be  a  no-op  if  a  gem  matching  the
+           requirements  is  in  the  bundle, and to raise a Gem::LoadError if
+           it's not
 
-       o   Define Gem.refresh to be a no-op, since the source index is	always
-	   frozen  when  using	bundler,  and  to prevent gems from the system
-	   leaking into the environment
+       o   Define Gem.refresh to be a no-op, since the source index is  always
+           frozen  when  using  bundler,  and  to prevent gems from the system
+           leaking into the environment
 
-       o   Override Gem.bin_path to use the gems in the bundle, making	system
-	   executables work
+       o   Override Gem.bin_path to use the gems in the bundle, making  system
+           executables work
 
        o   Add all gems in the bundle into Gem.loaded_specs
 
 
 
-       Finally, bundle exec also implicitly modifies Gemfile.lock if the lock-
-       file and the Gemfile do not match. Bundler needs the Gemfile to	deter-
-       mine  things  such as a gem's groups, autorequire, and platforms, etc.,
-       and that information isn't stored in  the  lockfile.  The  Gemfile  and
-       lockfile must be synced in order to bundle exec successfully, so bundle
-       exec updates the lockfile beforehand.
+       Finally,  bundle  exec  also  implicitly  modifies  Gemfile.lock if the
+       lockfile and the Gemfile do not match. Bundler  needs  the  Gemfile  to
+       determine  things  such  as a gem's groups, autorequire, and platforms,
+       etc., and that information isn't stored in the  lockfile.  The  Gemfile
+       and  lockfile  must  be synced in order to bundle exec successfully, so
+       bundle exec updates the lockfile beforehand.
 
    Loading
-       By default, when attempting to bundle exec to a file with a  ruby  she-
-       bang,  Bundler will Kernel.load that file instead of using Kernel.exec.
-       For the vast majority of cases, this is a performance improvement. In a
-       rare  few  cases,  this	could  cause some subtle side-effects (such as
-       dependence on the exact contents of $0 or __FILE__) and	the  optimiza-
-       tion can be disabled by enabling the disable_exec_load setting.
+       By default, when attempting to bundle  exec  to  a  file  with  a  ruby
+       shebang,   Bundler   will   Kernel.load  that  file  instead  of  using
+       Kernel.exec. For the vast majority of  cases,  this  is  a  performance
+       improvement.  In  a  rare  few  cases,  this  could  cause  some subtle
+       side-effects (such as  dependence  on  the  exact  contents  of  $0  or
+       __FILE__)  and  the  optimization  can  be  disabled  by  enabling  the
+       disable_exec_load setting.
 
    Shelling out
-       Any  Ruby  code that opens a subshell (like system, backticks, or %x{})
-       will automatically use the current Bundler environment. If you need  to
-       shell  out  to  a Ruby command that is not part of your current bundle,
-       use the with_clean_env method  with  a  block.  Any  subshells  created
-       inside  the  block will be given the environment present before Bundler
-       was activated. For example, Homebrew commands run Ruby, but don't  work
+       Any Ruby code that opens a subshell (like system, backticks,  or  %x{})
+       will  automatically use the current Bundler environment. If you need to
+       shell out to a Ruby command that is not part of  your  current  bundle,
+       use  the  with_clean_env  method  with  a  block. Any subshells created
+       inside the block will be given the environment present  before  Bundler
+       was  activated. For example, Homebrew commands run Ruby, but don't work
        inside a bundle:
 
 
 
-	   Bundler.with_clean_env do
-	     `brew install wget`
-	   end
+           Bundler.with_clean_env do
+             `brew install wget`
+           end
 
 
 
-       Using  with_clean_env  is  also	necessary if you are shelling out to a
-       different bundle. Any Bundler commands run in a subshell  will  inherit
-       the  current  Gemfile, so commands that need to run in the context of a
+       Using with_clean_env is also necessary if you are  shelling  out  to  a
+       different  bundle.  Any Bundler commands run in a subshell will inherit
+       the current Gemfile, so commands that need to run in the context  of  a
        different bundle also need to use with_clean_env.
 
 
 
-	   Bundler.with_clean_env do
-	     Dir.chdir "/other/bundler/project" do
-	       `bundle exec ./script`
-	     end
-	   end
+           Bundler.with_clean_env do
+             Dir.chdir "/other/bundler/project" do
+               `bundle exec ./script`
+             end
+           end
 
 
 
-       Bundler provides convenience helpers that wrap  system  and  exec,  and
+       Bundler  provides  convenience  helpers  that wrap system and exec, and
        they can be used like this:
 
 
 
-	   Bundler.clean_system('brew install wget')
-	   Bundler.clean_exec('brew install wget')
+           Bundler.clean_system('brew install wget')
+           Bundler.clean_exec('brew install wget')
 
 
 
 RUBYGEMS PLUGINS
-       At  present,  the  Rubygems  plugin  system  requires  all  files named
-       rubygems_plugin.rb on the load path of any installed gem when any  Ruby
+       At present,  the  Rubygems  plugin  system  requires  all  files  named
+       rubygems_plugin.rb  on the load path of any installed gem when any Ruby
        code requires rubygems.rb. This includes executables installed into the
        system, like rails, rackup, and rspec.
 
-       Since Rubygems plugins can contain arbitrary Ruby code,	they  commonly
+       Since  Rubygems  plugins can contain arbitrary Ruby code, they commonly
        end up activating themselves or their dependencies.
 
-       For  instance,  the gemcutter 0.5 gem depended on json_pure. If you had
-       that version of gemcutter installed (even if you also had a newer  ver-
-       sion  without  this problem), Rubygems would activate gemcutter 0.5 and
-       json_pure <latest>.
+       For instance, the gemcutter 0.5 gem depended on json_pure. If  you  had
+       that  version  of  gemcutter  installed  (even  if you also had a newer
+       version without this problem), Rubygems would  activate  gemcutter  0.5
+       and json_pure <latest>.
 
        If your Gemfile(5) also contained json_pure (or a gem with a dependency
-       on  json_pure),	the  latest version on your system might conflict with
-       the version in your Gemfile(5), or the snapshot version	in  your  Gem-
-       file.lock.
+       on json_pure), the latest version on your system  might  conflict  with
+       the  version  in  your  Gemfile(5),  or  the  snapshot  version in your
+       Gemfile.lock.
 
        If this happens, bundler will say:
 
 
 
-	   You have already activated json_pure 1.4.6 but your Gemfile
-	   requires json_pure 1.4.3. Consider using bundle exec.
+           You have already activated json_pure 1.4.6 but your Gemfile
+           requires json_pure 1.4.3. Consider using bundle exec.
 
 
 
-       In  this  situation, you almost certainly want to remove the underlying
-       gem with the problematic gem plugin. In general, the authors  of  these
-       plugins	(in this case, the gemcutter gem) have released newer versions
+       In this situation, you almost certainly want to remove  the  underlying
+       gem  with  the problematic gem plugin. In general, the authors of these
+       plugins (in this case, the gemcutter gem) have released newer  versions
        that are more careful in their plugins.
 
        You can find a list of all the gems containing gem plugins by running
 
 
 
-	   ruby -rrubygems -e "puts Gem.find_files('rubygems_plugin.rb')"
+           ruby -rrubygems -e "puts Gem.find_files('rubygems_plugin.rb')"
 
 
 
        At the very least, you should remove all but the newest version of each
-       gem  plugin, and also remove all gem plugins that you aren't using (gem
+       gem plugin, and also remove all gem plugins that you aren't using  (gem
        uninstall gem_name).
 
 
 
-				 December 2019			BUNDLE-EXEC(1)
+                                   July 2020                    BUNDLE-EXEC(1)

data/man/bundle-gem.1

@@ -1,7 +1,7 @@
 .\" generated with Ronn/v0.7.3
 .\" http://github.com/rtomayko/ronn/tree/0.7.3
 .
-.TH "BUNDLE\-GEM" "1" "December 2019" "" ""
+.TH "BUNDLE\-GEM" "1" "July 2020" "" ""
 .
 .SH "NAME"
 \fBbundle\-gem\fR \- Generate a project skeleton for creating a rubygem
@@ -64,8 +64,30 @@ Add an MIT license to a \fBLICENSE\.txt\fR file in the root of the generated pro
 Do not create a \fBLICENSE\.txt\fR (overrides \fB\-\-mit\fR specified in the global config)\.
 .
 .TP
-\fB\-t\fR, \fB\-\-test=minitest\fR, \fB\-\-test=rspec\fR
-Specify the test framework that Bundler should use when generating the project\. Acceptable values are \fBminitest\fR and \fBrspec\fR\. The \fBGEM_NAME\.gemspec\fR will be configured and a skeleton test/spec directory will be created based on this option\. If this option is unspecified, an interactive prompt will be displayed and the answer will be saved in Bundler\'s global config for future \fBbundle gem\fR use\. If no option is specified, the default testing framework is RSpec\.
+\fB\-t\fR, \fB\-\-test=minitest\fR, \fB\-\-test=rspec\fR, \fB\-\-test=test\-unit\fR
+Specify the test framework that Bundler should use when generating the project\. Acceptable values are \fBminitest\fR, \fBrspec\fR and \fBtest\-unit\fR\. The \fBGEM_NAME\.gemspec\fR will be configured and a skeleton test/spec directory will be created based on this option\. Given no option is specified:
+.
+.IP
+When Bundler is configured to generate tests, this defaults to Bundler\'s global config setting \fBgem\.test\fR\.
+.
+.IP
+When Bundler is configured to not generate tests, an interactive prompt will be displayed and the answer will be used for the current rubygem project\.
+.
+.IP
+When Bundler is unconfigured, an interactive prompt will be displayed and the answer will be saved in Bundler\'s global config for future \fBbundle gem\fR use\.
+.
+.TP
+\fB\-\-ci\fR, \fB\-\-ci=github\fR, \fB\-\-ci=travis\fR, \fB\-\-ci=gitlab\fR, \fB\-\-ci=circle\fR
+Specify the continuous integration service that Bundler should use when generating the project\. Acceptable values are \fBgithub\fR, \fBtravis\fR, \fBgitlab\fR and \fBcircle\fR\. A configuration file will be generated in the project directory\. Given no option is specified:
+.
+.IP
+When Bundler is configured to generate CI files, this defaults to Bundler\'s global config setting \fBgem\.ci\fR\.
+.
+.IP
+When Bundler is configured to not generate CI files, an interactive prompt will be displayed and the answer will be used for the current rubygem project\.
+.
+.IP
+When Bundler is unconfigured, an interactive prompt will be displayed and the answer will be saved in Bundler\'s global config for future \fBbundle gem\fR use\.
 .
 .TP
 \fB\-e\fR, \fB\-\-edit[=EDITOR]\fR

data/man/bundle-gem.1.txt

@@ -1,4 +1,4 @@
-BUNDLE-GEM(1)							 BUNDLE-GEM(1)
+BUNDLE-GEM(1)                                                    BUNDLE-GEM(1)
 
 
 
@@ -16,8 +16,8 @@ DESCRIPTION
        Run  rake -T in the resulting project for a list of Rake tasks that can
        be used to test and publish the gem to rubygems.org.
 
-       The generated project skeleton  can  be	customized  with  OPTIONS,  as
-       explained  below.  Note	that  these  options can also be specified via
+       The generated project skeleton  can  be  customized  with  OPTIONS,  as
+       explained  below.  Note  that  these  options can also be specified via
        Bundler's global configuration file using the following names:
 
        o   gem.coc
@@ -30,55 +30,81 @@ DESCRIPTION
 
 OPTIONS
        --exe or -b or --bin
-	      Specify that Bundler  should  create  a  binary  executable  (as
-	      exe/GEM_NAME) in the generated rubygem project. This binary will
-	      also be added to the GEM_NAME.gemspec manifest. This behavior is
-	      disabled by default.
+              Specify that Bundler  should  create  a  binary  executable  (as
+              exe/GEM_NAME) in the generated rubygem project. This binary will
+              also be added to the GEM_NAME.gemspec manifest. This behavior is
+              disabled by default.
 
        --no-exe
-	      Do  not create a binary (overrides --exe specified in the global
-	      config).
+              Do  not create a binary (overrides --exe specified in the global
+              config).
 
-       --coc  Add a CODE_OF_CONDUCT.md file  to  the  root  of	the  generated
-	      project.	If  this  option is unspecified, an interactive prompt
-	      will be displayed and the answer	will  be  saved  in  Bundler's
-	      global config for future bundle gem use.
+       --coc  Add a CODE_OF_CONDUCT.md file  to  the  root  of  the  generated
+              project.  If  this  option is unspecified, an interactive prompt
+              will be displayed and the answer  will  be  saved  in  Bundler's
+              global config for future bundle gem use.
 
        --no-coc
-	      Do not create a CODE_OF_CONDUCT.md (overrides --coc specified in
-	      the global config).
+              Do not create a CODE_OF_CONDUCT.md (overrides --coc specified in
+              the global config).
 
        --ext  Add boilerplate for C extension code to the  generated  project.
-	      This behavior is disabled by default.
+              This behavior is disabled by default.
 
        --no-ext
-	      Do  not  add  C extension code (overrides --ext specified in the
-	      global config).
+              Do  not  add  C extension code (overrides --ext specified in the
+              global config).
 
-       --mit  Add an MIT license to a LICENSE.txt file in the root of the gen-
-	      erated project. Your name from the global git config is used for
-	      the copyright statement.	If  this  option  is  unspecified,  an
-	      interactive  prompt  will  be  displayed	and the answer will be
-	      saved in Bundler's global config for future bundle gem use.
+       --mit  Add an MIT license to a LICENSE.txt file  in  the  root  of  the
+              generated  project. Your name from the global git config is used
+              for the copyright statement. If this option is  unspecified,  an
+              interactive  prompt  will  be  displayed  and the answer will be
+              saved in Bundler's global config for future bundle gem use.
 
        --no-mit
-	      Do not create a LICENSE.txt (overrides --mit  specified  in  the
-	      global config).
-
-       -t, --test=minitest, --test=rspec
-	      Specify the test framework that Bundler should use when generat-
-	      ing the project. Acceptable values are minitest and  rspec.  The
-	      GEM_NAME.gemspec	will  be  configured  and a skeleton test/spec
-	      directory will be created based on this option. If  this	option
-	      is  unspecified, an interactive prompt will be displayed and the
-	      answer will be saved in Bundler's global config for future  bun-
-	      dle  gem	use.  If  no  option is specified, the default testing
-	      framework is RSpec.
+              Do not create a LICENSE.txt (overrides --mit  specified  in  the
+              global config).
+
+       -t, --test=minitest, --test=rspec, --test=test-unit
+              Specify   the  test  framework  that  Bundler  should  use  when
+              generating the project. Acceptable values  are  minitest,  rspec
+              and  test-unit.  The  GEM_NAME.gemspec  will be configured and a
+              skeleton test/spec directory  will  be  created  based  on  this
+              option. Given no option is specified:
+
+              When  Bundler  is configured to generate tests, this defaults to
+              Bundler's global config setting gem.test.
+
+              When Bundler is configured to not generate tests, an interactive
+              prompt  will  be  displayed  and the answer will be used for the
+              current rubygem project.
+
+              When Bundler is unconfigured,  an  interactive  prompt  will  be
+              displayed  and  the  answer  will  be  saved in Bundler's global
+              config for future bundle gem use.
+
+       --ci, --ci=github, --ci=travis, --ci=gitlab, --ci=circle
+              Specify the continuous integration service that  Bundler  should
+              use  when  generating the project. Acceptable values are github,
+              travis,  gitlab  and  circle.  A  configuration  file  will   be
+              generated   in   the  project  directory.  Given  no  option  is
+              specified:
+
+              When Bundler is configured to generate CI files,  this  defaults
+              to Bundler's global config setting gem.ci.
+
+              When  Bundler  is  configured  to  not  generate  CI  files,  an
+              interactive prompt will be displayed and the answer will be used
+              for the current rubygem project.
+
+              When  Bundler  is  unconfigured,  an  interactive prompt will be
+              displayed and the answer  will  be  saved  in  Bundler's  global
+              config for future bundle gem use.
 
        -e, --edit[=EDITOR]
-	      Open the resulting GEM_NAME.gemspec in EDITOR,  or  the  default
-	      editor  if  not specified. The default is $BUNDLER_EDITOR, $VIS-
-	      UAL, or $EDITOR.
+              Open  the  resulting  GEM_NAME.gemspec in EDITOR, or the default
+              editor  if  not  specified.  The  default  is   $BUNDLER_EDITOR,
+              $VISUAL, or $EDITOR.
 
 SEE ALSO
        o   bundle config(1) bundle-config.1.html
@@ -88,4 +114,4 @@ SEE ALSO
 
 
 
-				 December 2019			 BUNDLE-GEM(1)
+                                   July 2020                     BUNDLE-GEM(1)