https://github.com/rubygems/rubygems/commit/02de767e14

https://github.com/rubygems/rubygems/commit/9691097036

This option is similar to the `bundle install --quiet` option

https://github.com/rubygems/rubygems/commit/3bd773d827

https://github.com/rubygems/rubygems/commit/3434f094a2

If Gemfile is empty and there's no lockfile (situation after `bundle init`), and
`frozen` is configured, running `bundle add` will result in an strange
error, like this:

```
$ bundle add rake
, but the lockfile can't be updated because frozen mode is set

You have deleted from the Gemfile:
* rake (~> 13.2)

Run `bundle install` elsewhere and add the updated Gemfile to version control.
```

This commit fixes the problem to instead print

https://github.com/rubygems/rubygems/commit/152331a9dc

https://github.com/rubygems/rubygems/commit/6d2cf955f9

Bundler online documentation says that if the gem is located within a subdirectory of a git repository,
you can use the `:glob` option to specify the location of its .gemspec

`gem 'cf-copilot', git: 'https://github.com/cloudfoundry/copilot', glob: 'sdk/ruby/*.gemspec'`

This change allows for equivalent functionality from the bundler CLI

`bundle add cf-copilot --git=https://github.com/cloudfoundry/copilot --glob=sdk/ruby/*.gemspec`

https://github.com/rubygems/rubygems/commit/91052e5868

https://github.com/rubygems/rubygems/commit/bb66253f2c