| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
With markup
[`bundle platform(1)`][bundle-platform(1)]
ronn creates this HTML fragment
<dt><a href="bundle-platform.html"><code>bundle platform(1)</code></a></dt><dd><p>Display platform compatibility information</p></dd>
At the same time, it generates HTML file `bundle-platform.1.html` based on the
man page section, and this results in certain inter-man-page links 404.
We resolve this inconsistency by spelling out the href attributes.
|
|\
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Update docs to reflect revised guidance to check in locks for gems
Thanks so much for the contribution!
To make reviewing this PR a bit easier, please fill out answers to the following questions.
### What was the end-user problem that led to this PR?
The problem was...
- Bundler stopped gitignoring gem locks. The change was merged in but we need to reflect that change in documentation.
### What was your diagnosis of the problem?
My diagnosis was...
- To add in documentation explaining why Bunder now does _not_ gitignore gem locks.
### What is your fix for the problem, implemented in this PR?
My fix...
- Update the `gemfile.lock` section of `bundle install` man pages as well as the `gemfile` man page.
### Why did you choose this fix out of the possible options?
I chose this fix because...
- This addresses open issue https://github.com/bundler/bundler/issues/5879
|
| |
| |
| |
| |
| |
| | |
After reviewing, I think the question and answer is a bad fit for the
`gemfile` man page. It does seem like a good fit for the FAQ page on the
Bundler documentation site, though, and I'll add it over there.
|
| | |
|
|/ |
|
|\
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Added a sentence to `binstubs`
Per feedback from @arbonap, we've added a sentence that briefly explains what binstubs is to the binstubs section.
Thanks so much for the contribution!
To make reviewing this PR a bit easier, please fill out answers to the following questions.
### What was the end-user problem that led to this PR?
The problem was...no understanding of what binstubs is. Added a quick two sentences!
### What was your diagnosis of the problem?
My diagnosis was...we needed some language there. @arbonap and @indirect pointed this out and offered the explanations.
### What is your fix for the problem, implemented in this PR?
My fix...was to turn their explanations into simple language!
### Why did you choose this fix out of the possible options?
I chose this fix because...it'll help users understand binstubs better
|
| |
| |
| | |
from line 54
|
| |
| |
| | |
(Fingers crossed!)
|
| |
| |
| | |
From line 51
|
| |
| |
| | |
Per feedback from @arbonap, we've added a sentence that briefly explains what binstubs is to the binstubs section.
|
| | |
|
|/ |
|
| |
|
| |
|
| |
|
|
|
|
| |
This option has existed since v1.1 and we're currently on v1.11!
|
| |
|
| |
|
| |
|
| |
|
| |
|
|\
| |
| |
| |
| | |
Clarify the purpose of --deployment
[ci skip]
|
| |
| |
| |
| |
| | |
The man page originally explained that `--deployment` is not appropriate for the `test` environment, which is misleading. In a CI environment, you *do* want to use `--deployment`, despite the fact that CI will likely be using `RAILS_ENV=test` when running tests.
This PR clarifies that `--deployment` is for production and CI, and avoids explicitly referencing Rails environment names.
|
|/ |
|
|
|
|
|
|
|
|
| |
Version 1.9.4
Conflicts:
lib/bundler/installer.rb
lib/bundler/match_platform.rb
lib/bundler/source/rubygems.rb
|
|
|
|
|
|
|
|
|
| |
* Add optional option to the group method, defaulting to false
* Exclude optional groups from the groups to be installed
* Add --with parameter to bundle install to install a group that would
* otherwise be excluded
* Error out if a group is listed in both, --with and --without
* Add bundle_with option to capistrano task
|
|
|
| |
Change "as it will cause in an error" to "as it will cause an error".
|
|
|
|
| |
be styleguideish and use singleticks in Gemfile examples
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
--deploymet, --path and --system
be strict with Bundler capitalized like a fine Product
explain what --clean does
fix typos
|
|
|
|
|
|
| |
be consistent referring to Rubygems et al.
try to give better explanations
cleanup
|
|
|
|
| |
have 'official' english wording ("retry for a number of times")
|
| |
|
| |
|
|
|
|
| |
...since it's not user facing.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Conflicts:
CHANGELOG.md
Rakefile
lib/bundler/installer.rb
lib/bundler/rubygems_ext.rb
lib/bundler/source/rubygems.rb
spec/realworld/parallel_install_spec.rb
spec/realworld/parallel_update_spec.rb
|
| |
|
|
|
|
|
| |
refs #2667
[ci skip]
|
|
|
|
| |
Also added --jobs option to man file
|
| |
|
| |
|
|
|
|
|
|
| |
if https is the best way to access rubygems.org
then it should be default everywhere
including in examples on the man page
|
| |
|
| |
|
|
|
|
| |
OK. fixes #1475.
|
|\ |
|
| | |
|