summaryrefslogtreecommitdiff
path: root/man/bundle-gem.1.txt
diff options
context:
space:
mode:
Diffstat (limited to 'man/bundle-gem.1.txt')
-rw-r--r--man/bundle-gem.1.txt78
1 files changed, 39 insertions, 39 deletions
diff --git a/man/bundle-gem.1.txt b/man/bundle-gem.1.txt
index 554bb1a41b..d645bfe7e2 100644
--- a/man/bundle-gem.1.txt
+++ b/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,55 @@ 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. 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. If no option is
+ specified, the default testing framework is RSpec.
-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 +88,4 @@ SEE ALSO
- January 2020 BUNDLE-GEM(1)
+ May 2020 BUNDLE-GEM(1)