." generated with Ronn-NG/v0.10.1 ." github.com/apjanke/ronn-ng/tree/0.10.1 .TH “BUNDLE-GEM” “1” “July 2025” “” .SH “NAME” fBbundle-gemfR - Generate a project skeleton for creating a rubygem .SH “SYNOPSIS” fBbundle gemfR fIGEM_NAMEfR fIOPTIONSfR .SH “DESCRIPTION” Generates a directory named fBGEM_NAMEfR with a fBRakefilefR, fBGEM_NAME.gemspecfR, and other supporting files and directories that can be used to develop a rubygem with that name. .P Run fBrake -TfR in the resulting project for a list of Rake tasks that can be used to test and publish the gem to rubygems.org. .P 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: .IP “(bu” 4 fBgem.cocfR .IP “(bu” 4 fBgem.mitfR .IP “(bu” 4 fBgem.testfR .IP “” 0 .SH “OPTIONS” .TP fB--exefR, fB--binfR, fB-bfR Specify that Bundler should create a binary executable (as fBexe/GEM_NAMEfR) in the generated rubygem project. This binary will also be added to the fBGEM_NAME.gemspecfR manifest. This behavior is disabled by default. .TP fB--no-exefR Do not create a binary (overrides fB--exefR specified in the global config). .TP fB--cocfR Add a fBCODE_OF_CONDUCT.mdfR 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 fBbundle gemfR use. .TP fB--no-cocfR Do not create a fBCODE_OF_CONDUCT.mdfR (overrides fB--cocfR specified in the global config). .TP fB--changelogfR Add a fBCHANGELOG.mdfR 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 fBbundle gemfR use. Update the default with fBbundle config set --global gem.changelog <true|false>fR. .TP fB--no-changelogfR Do not create a fBCHANGELOG.mdfR (overrides fB--changelogfR specified in the global config). .TP fB--ext=cfR, fB--ext=rustfR Add boilerplate for C or Rust (currently magnus fIdocs.rs/magnusfR based) extension code to the generated project. This behavior is disabled by default. .TP fB--no-extfR Do not add extension code (overrides fB--extfR specified in the global config). .TP fB--gitfR Initialize a git repo inside your library. .TP fB--github-username=GITHUB_USERNAMEfR Fill in GitHub username on README so that you don’t have to do it manually. Set a default with fBbundle config set --global gem.github_username <your_username>fR. .TP fB--mitfR Add an MIT license to a fBLICENSE.txtfR 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 fBbundle gemfR use. .TP fB--no-mitfR Do not create a fBLICENSE.txtfR (overrides fB--mitfR specified in the global config). .TP fB-tfR, fB--test=minitestfR, fB--test=rspecfR, fB--test=test-unitfR Specify the test framework that Bundler should use when generating the project. Acceptable values are fBminitestfR, fBrspecfR and fBtest-unitfR. The fBGEM_NAME.gemspecfR 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.testfR. .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 gemfR use. .TP fB--no-testfR Do not use a test framework (overrides fB--testfR specified in the global config). .TP fB--cifR, fB--ci=circlefR, fB--ci=githubfR, fB--ci=gitlabfR Specify the continuous integration service that Bundler should use when generating the project. Acceptable values are fBgithubfR, fBgitlabfR and fBcirclefR. 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.cifR. .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 gemfR use. .TP fB--no-cifR Do not use a continuous integration service (overrides fB--cifR specified in the global config). .TP fB--linterfR, fB--linter=rubocopfR, fB--linter=standardfR Specify the linter and code formatter that Bundler should add to the project’s development dependencies. Acceptable values are fBrubocopfR and fBstandardfR. A configuration file will be generated in the project directory. Given no option is specified: .IP When Bundler is configured to add a linter, this defaults to Bundler’s global config setting fBgem.linterfR. .IP When Bundler is configured not to add a linter, 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 gemfR use. .TP fB--no-linterfR Do not add a linter (overrides fB--linterfR specified in the global config). .TP fB--rubocopfR Add rubocop to the generated Rakefile and gemspec. Set a default with fBbundle config set --global gem.rubocop truefR. .TP fB--edit=EDITfR, fB-e=EDITfR Open the resulting GEM_NAME.gemspec in EDIT, or the default editor if not specified. The default is fB$BUNDLER_EDITORfR, fB$VISUALfR, or fB$EDITORfR. .TP fB--bundlefR Run fBbundle installfR after creating the gem. .TP fB--no-bundlefR Do not run fBbundle installfR after creating the gem. .SH “SEE ALSO” .IP “(bu” 4 bundle config(1) fIbundle-config.1.htmlfR .IP “” 0