<feed xmlns='http://www.w3.org/2005/Atom'>
<title>delta/bundler.git, branch git_option_to_bundle_gem</title>
<subtitle>github.com: bundler/bundler.git
</subtitle>
<link rel='alternate' type='text/html' href='http://trove.baserock.org/cgit/delta/bundler.git/'/>
<entry>
<title>Add `--[no-]git` option to `bundle gem`</title>
<updated>2019-07-31T15:25:40+00:00</updated>
<author>
<name>David Rodríguez</name>
<email>deivid.rodriguez@riseup.net</email>
</author>
<published>2019-07-24T10:24:55+00:00</published>
<link rel='alternate' type='text/html' href='http://trove.baserock.org/cgit/delta/bundler.git/commit/?id=154c687310396bc6a1ca06b853dc9f3eca8c6a81'/>
<id>154c687310396bc6a1ca06b853dc9f3eca8c6a81</id>
<content type='text'>
I think using `--no-git` can be useful when creating gems inside
monorepos.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
I think using `--no-git` can be useful when creating gems inside
monorepos.
</pre>
</div>
</content>
</entry>
<entry>
<title>Merge #7123</title>
<updated>2019-07-31T14:45:58+00:00</updated>
<author>
<name>Bundlerbot</name>
<email>bot@bundler.io</email>
</author>
<published>2019-07-31T14:45:58+00:00</published>
<link rel='alternate' type='text/html' href='http://trove.baserock.org/cgit/delta/bundler.git/commit/?id=33199fd0a32fe074393fc85f27a37b1f0a1eb85e'/>
<id>33199fd0a32fe074393fc85f27a37b1f0a1eb85e</id>
<content type='text'>
7123: Refactors to `bundle outdated` r=deivid-rodriguez a=ryanfox1985

### What was the end-user problem that led to this PR?

Code in `bundle outdated` code be simpler and more readable.

### What is your fix for the problem, implemented in this PR?

My fix is to refactor the command.

Co-authored-by: Guillermo Guerrero &lt;wolf.fox1985@gmail.com&gt;
Co-authored-by: David Rodríguez &lt;deivid.rodriguez@riseup.net&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
7123: Refactors to `bundle outdated` r=deivid-rodriguez a=ryanfox1985

### What was the end-user problem that led to this PR?

Code in `bundle outdated` code be simpler and more readable.

### What is your fix for the problem, implemented in this PR?

My fix is to refactor the command.

Co-authored-by: Guillermo Guerrero &lt;wolf.fox1985@gmail.com&gt;
Co-authored-by: David Rodríguez &lt;deivid.rodriguez@riseup.net&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>Merge #7265</title>
<updated>2019-07-31T10:38:14+00:00</updated>
<author>
<name>Bundlerbot</name>
<email>bot@bundler.io</email>
</author>
<published>2019-07-31T10:38:14+00:00</published>
<link rel='alternate' type='text/html' href='http://trove.baserock.org/cgit/delta/bundler.git/commit/?id=acc4ab8be92c9f26a62311f94771eb7bf31ee340'/>
<id>acc4ab8be92c9f26a62311f94771eb7bf31ee340</id>
<content type='text'>
7265: Fix incorrect sectioning in `gemfile` man page r=deivid-rodriguez a=deivid-rodriguez

### What was the end-user problem that led to this PR?

The problem was that Gemfile's man page has incorrect syntax in the section where examples for `:ref`, `:tag` and `:branch` are given.

### What was your diagnosis of the problem?

My diagnosis was that the section was incorrect since the examples were listed as a separate section. Also, the syntax seems incorrect, since building the docs with [ronn-ng]() (something I've been experimenting with lately) gives the following error:

```
$ bin/rake man/gemfile.5
/home/deivid/.rbenv/versions/2.6.3/bin/ruby -S ronn --roff --pipe man/gemfile.5.ronn &gt; man/gemfile.5
warn: unrecognized inline tag: ["p"]
warn: unrecognized inline tag: ["p"]
warn: unrecognized inline tag: ["p"]
man/gemfile.5 ran for   0.000305   0.000038   0.317832 (  0.317939)
```

### What is your fix for the problem, implemented in this PR?

My fix is to correct the syntax. The comparison of the rendered man page is:

#### `bundle help gemfile` (before)

```
   (...)
       branch, tag, and ref
              You MUST only specify at most one of these options. The default is :branch =&gt; "master"

       For example:

       submodules
              For  reference,  a  git  submodule https://git-scm.com/book/en/v2/Git-Tools-Submodules lets you have another git repository within a subfolder of your
              repository. Specify :submodules =&gt; true to cause bundler to expand any submodules included in the git repository
   (...)
```

#### `bundle help gemfile` (after)

```
   (...)
       branch, tag, and ref
              You MUST only specify at most one of these options. The default is :branch =&gt; "master". For example:

              git "https://github.com/rails/rails.git", :branch =&gt; "5-0-stable" do

              git "https://github.com/rails/rails.git", :tag =&gt; "v5.0.0" do

              git "https://github.com/rails/rails.git", :ref =&gt; "4aded" do

       submodules
              For  reference,  a  git  submodule https://git-scm.com/book/en/v2/Git-Tools-Submodules lets you have another git repository within a subfolder of your
              repository. Specify :submodules =&gt; true to cause bundler to expand any submodules included in the git repository
   (...)
```

### Why did you choose this fix out of the possible options?

I chose this fix because it seems like the right thing to do.


Co-authored-by: David Rodríguez &lt;deivid.rodriguez@riseup.net&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
7265: Fix incorrect sectioning in `gemfile` man page r=deivid-rodriguez a=deivid-rodriguez

### What was the end-user problem that led to this PR?

The problem was that Gemfile's man page has incorrect syntax in the section where examples for `:ref`, `:tag` and `:branch` are given.

### What was your diagnosis of the problem?

My diagnosis was that the section was incorrect since the examples were listed as a separate section. Also, the syntax seems incorrect, since building the docs with [ronn-ng]() (something I've been experimenting with lately) gives the following error:

```
$ bin/rake man/gemfile.5
/home/deivid/.rbenv/versions/2.6.3/bin/ruby -S ronn --roff --pipe man/gemfile.5.ronn &gt; man/gemfile.5
warn: unrecognized inline tag: ["p"]
warn: unrecognized inline tag: ["p"]
warn: unrecognized inline tag: ["p"]
man/gemfile.5 ran for   0.000305   0.000038   0.317832 (  0.317939)
```

### What is your fix for the problem, implemented in this PR?

My fix is to correct the syntax. The comparison of the rendered man page is:

#### `bundle help gemfile` (before)

```
   (...)
       branch, tag, and ref
              You MUST only specify at most one of these options. The default is :branch =&gt; "master"

       For example:

       submodules
              For  reference,  a  git  submodule https://git-scm.com/book/en/v2/Git-Tools-Submodules lets you have another git repository within a subfolder of your
              repository. Specify :submodules =&gt; true to cause bundler to expand any submodules included in the git repository
   (...)
```

#### `bundle help gemfile` (after)

```
   (...)
       branch, tag, and ref
              You MUST only specify at most one of these options. The default is :branch =&gt; "master". For example:

              git "https://github.com/rails/rails.git", :branch =&gt; "5-0-stable" do

              git "https://github.com/rails/rails.git", :tag =&gt; "v5.0.0" do

              git "https://github.com/rails/rails.git", :ref =&gt; "4aded" do

       submodules
              For  reference,  a  git  submodule https://git-scm.com/book/en/v2/Git-Tools-Submodules lets you have another git repository within a subfolder of your
              repository. Specify :submodules =&gt; true to cause bundler to expand any submodules included in the git repository
   (...)
```

### Why did you choose this fix out of the possible options?

I chose this fix because it seems like the right thing to do.


Co-authored-by: David Rodríguez &lt;deivid.rodriguez@riseup.net&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>Merge #7268</title>
<updated>2019-07-30T09:04:56+00:00</updated>
<author>
<name>Bundlerbot</name>
<email>bot@bundler.io</email>
</author>
<published>2019-07-30T09:04:56+00:00</published>
<link rel='alternate' type='text/html' href='http://trove.baserock.org/cgit/delta/bundler.git/commit/?id=78675d764944335451a4ccea79d11352ec6da55e'/>
<id>78675d764944335451a4ccea79d11352ec6da55e</id>
<content type='text'>
7268: Fix typo in binstubs documentation r=hsbt a=scotttesler

### What was the end-user problem that led to this PR?

There is a typo in the [binstubs documentation](https://bundler.io/v2.0/man/bundle-binstubs.1.html).

It currently reads 

&gt; This gives you a file that can **by** run directly

It should read 

&gt; This gives you a file that can **be** run directly


![Screen Shot 2019-07-29 at 3 14 24 PM](https://user-images.githubusercontent.com/586779/62079346-2452b180-b214-11e9-84c6-e2661c60eb4a.png)

### What is your fix for the problem, implemented in this PR?

Fix the typo in the RONN file that is used to generate this documentation.

Co-authored-by: Scott Tesler &lt;scottiet123@gmail.com&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
7268: Fix typo in binstubs documentation r=hsbt a=scotttesler

### What was the end-user problem that led to this PR?

There is a typo in the [binstubs documentation](https://bundler.io/v2.0/man/bundle-binstubs.1.html).

It currently reads 

&gt; This gives you a file that can **by** run directly

It should read 

&gt; This gives you a file that can **be** run directly


![Screen Shot 2019-07-29 at 3 14 24 PM](https://user-images.githubusercontent.com/586779/62079346-2452b180-b214-11e9-84c6-e2661c60eb4a.png)

### What is your fix for the problem, implemented in this PR?

Fix the typo in the RONN file that is used to generate this documentation.

Co-authored-by: Scott Tesler &lt;scottiet123@gmail.com&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>Fix typo in binstubs documentation</title>
<updated>2019-07-29T20:15:37+00:00</updated>
<author>
<name>Scott Tesler</name>
<email>ScottieT123@gmail.com</email>
</author>
<published>2019-07-29T20:15:37+00:00</published>
<link rel='alternate' type='text/html' href='http://trove.baserock.org/cgit/delta/bundler.git/commit/?id=88dbfa18b4e61f0cd9aa8998f9e0f00ea73729b7'/>
<id>88dbfa18b4e61f0cd9aa8998f9e0f00ea73729b7</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>Merge #7259</title>
<updated>2019-07-29T07:57:34+00:00</updated>
<author>
<name>Bundlerbot</name>
<email>bot@bundler.io</email>
</author>
<published>2019-07-29T07:57:34+00:00</published>
<link rel='alternate' type='text/html' href='http://trove.baserock.org/cgit/delta/bundler.git/commit/?id=3af2211195811e1e0618c166387a53a677ab1438'/>
<id>3af2211195811e1e0618c166387a53a677ab1438</id>
<content type='text'>
7259: Relax bundler binstub r=indirect a=deivid-rodriguez

### What was the end-user problem that led to this PR?

The problem was that the logic to select bundler versions was different when bundler is run from a rubygems binstub that when bundler is run from a bundler binstub.

### What was your diagnosis of the problem?

My diagnosis was that we should unify the logic.

### What is your fix for the problem, implemented in this PR?

My fix is to use the same logic implemented in the rubygems version finder, namely, only fail if the major version of bundler does not match.

### Why did you choose this fix out of the possible options?

I chose this fix because it makes things consistent.

Fixes #7243.


Co-authored-by: David Rodríguez &lt;deivid.rodriguez@riseup.net&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
7259: Relax bundler binstub r=indirect a=deivid-rodriguez

### What was the end-user problem that led to this PR?

The problem was that the logic to select bundler versions was different when bundler is run from a rubygems binstub that when bundler is run from a bundler binstub.

### What was your diagnosis of the problem?

My diagnosis was that we should unify the logic.

### What is your fix for the problem, implemented in this PR?

My fix is to use the same logic implemented in the rubygems version finder, namely, only fail if the major version of bundler does not match.

### Why did you choose this fix out of the possible options?

I chose this fix because it makes things consistent.

Fixes #7243.


Co-authored-by: David Rodríguez &lt;deivid.rodriguez@riseup.net&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>Merge #7258</title>
<updated>2019-07-29T06:57:57+00:00</updated>
<author>
<name>Bundlerbot</name>
<email>bot@bundler.io</email>
</author>
<published>2019-07-29T06:57:57+00:00</published>
<link rel='alternate' type='text/html' href='http://trove.baserock.org/cgit/delta/bundler.git/commit/?id=cdd2075c71e2426e6fd77c1a340620753b14669e'/>
<id>cdd2075c71e2426e6fd77c1a340620753b14669e</id>
<content type='text'>
7258: Restore the removal of the `--all` flag for `bundle cache` in Bundler 3 r=indirect a=deivid-rodriguez

### What was the end-user problem that led to this PR?

The problem was that I accidentally restored this flag on Bundler 3 in #7249, but the plan still is to remove it.

### What was your diagnosis of the problem?

My diagnosis was that I need to remove it again.

### What is your fix for the problem, implemented in this PR?

My fix is to remove it.

### Why did you choose this fix out of the possible options?

I chose this fix because it's the original plan and makes sense.


Co-authored-by: David Rodríguez &lt;deivid.rodriguez@riseup.net&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
7258: Restore the removal of the `--all` flag for `bundle cache` in Bundler 3 r=indirect a=deivid-rodriguez

### What was the end-user problem that led to this PR?

The problem was that I accidentally restored this flag on Bundler 3 in #7249, but the plan still is to remove it.

### What was your diagnosis of the problem?

My diagnosis was that I need to remove it again.

### What is your fix for the problem, implemented in this PR?

My fix is to remove it.

### Why did you choose this fix out of the possible options?

I chose this fix because it's the original plan and makes sense.


Co-authored-by: David Rodríguez &lt;deivid.rodriguez@riseup.net&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>Fix `git` options examples</title>
<updated>2019-07-26T09:39:56+00:00</updated>
<author>
<name>David Rodríguez</name>
<email>deivid.rodriguez@riseup.net</email>
</author>
<published>2019-07-26T09:39:41+00:00</published>
<link rel='alternate' type='text/html' href='http://trove.baserock.org/cgit/delta/bundler.git/commit/?id=bda0fa02c451584681d21ab35fd700db21e66f03'/>
<id>bda0fa02c451584681d21ab35fd700db21e66f03</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>Fix incorrect sectioning in `gemfile` man page</title>
<updated>2019-07-26T09:39:55+00:00</updated>
<author>
<name>David Rodríguez</name>
<email>deivid.rodriguez@riseup.net</email>
</author>
<published>2019-07-25T08:43:36+00:00</published>
<link rel='alternate' type='text/html' href='http://trove.baserock.org/cgit/delta/bundler.git/commit/?id=428f53bef02ba6d3855d3d55d9133b349f5e3978'/>
<id>428f53bef02ba6d3855d3d55d9133b349f5e3978</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>Merge #7257</title>
<updated>2019-07-26T07:13:34+00:00</updated>
<author>
<name>Bundlerbot</name>
<email>bot@bundler.io</email>
</author>
<published>2019-07-26T07:13:34+00:00</published>
<link rel='alternate' type='text/html' href='http://trove.baserock.org/cgit/delta/bundler.git/commit/?id=d875be710a1a5cccacdcc8eea4ffd49c1f036bb8'/>
<id>d875be710a1a5cccacdcc8eea4ffd49c1f036bb8</id>
<content type='text'>
7257: Get some more Windows specs passing r=deivid-rodriguez a=deivid-rodriguez

### What was the end-user problem that led to this PR?

The problem was that Windows build is still red.

### What was your diagnosis of the problem?

My diagnosis was that some functionality is actually working, but specs need to be adapted, because some error messages include the platform on Windows.

### What is your fix for the problem, implemented in this PR?

My fix is to use `force_ruby_platform` for those specs.

### Why did you choose this fix out of the possible options?

I chose this fix because... I'm not sure, maybe it's better to adapt the error messages to include the platform when run on Windows.

Co-authored-by: David Rodríguez &lt;deivid.rodriguez@riseup.net&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
7257: Get some more Windows specs passing r=deivid-rodriguez a=deivid-rodriguez

### What was the end-user problem that led to this PR?

The problem was that Windows build is still red.

### What was your diagnosis of the problem?

My diagnosis was that some functionality is actually working, but specs need to be adapted, because some error messages include the platform on Windows.

### What is your fix for the problem, implemented in this PR?

My fix is to use `force_ruby_platform` for those specs.

### Why did you choose this fix out of the possible options?

I chose this fix because... I'm not sure, maybe it's better to adapt the error messages to include the platform when run on Windows.

Co-authored-by: David Rodríguez &lt;deivid.rodriguez@riseup.net&gt;
</pre>
</div>
</content>
</entry>
</feed>
