bundle outdated --source not working as expected
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 4k
- Forks
- 1.9k
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 81
Description
The help for bundle outdated states:
[--source=Check against a specific source]
I expect that I could use this to check outdated gems not against our internal rubygems host defined in my Gemfile, but against rubygems.org by executing bundle outdated --source rubygems.org.
But according to the output it still connects to our internal gem server and not rubygems.org.
Do I use it wrong, is this a bug or does the option mean something different than I would expect it to mean?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing bundle outdated --source rubygems.org with a Gemfile that uses an internal gem server, then inspect the bundle outdated command's source-selection behavior and help text. Done means either the command checks rubygems.org as documented or the help clearly explains the option's actual meaning.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- cli, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100