Skip to content
This repository has been archived by the owner on Jun 5, 2019. It is now read-only.

Add --all flag to bundler update #18

Closed
xaviershay opened this issue Aug 21, 2013 · 3 comments
Closed

Add --all flag to bundler update #18

xaviershay opened this issue Aug 21, 2013 · 3 comments
Labels
in progress incompatible ui

Comments

@xaviershay
Copy link
Contributor

Print usage when bundle update is run without arguments -- many people think that they should run bundle update after git pull, but that mostly just messes everything up.

From rubygems/bundler#2279
@jlsuttles
Copy link

So the current functionality when one runs bundle update should happen when one runs bundle update --all and bundle update should just print usage instructions.

@indirect
Copy link
Member

Yup. Since this change breaks backwards compatibility, pull requests should be sent to the 2-0-dev branch instead of master.

On Sep 13, 2013, at 4:38 PM, Jessica Lynn Suttles notifications@github.com wrote:

So the current functionality when one runs bundle update should happen when one runs bundle update --all and bundle update should just print usage instructions.

—
Reply to this email directly or view it on GitHub.

@jhhere jhhere mentioned this issue Sep 16, 2013
Merged
@jhhere jhhere mentioned this issue Sep 24, 2013
Merged
@sheerun sheerun mentioned this issue Nov 10, 2014
Closed
mvz pushed a commit to mvz/bundler that referenced this issue Jan 3, 2015
@jhhere
Move bundle update functionality to bundle update -all
6709250 
Bundle update should just print usage instructions.
rubygems/bundler-features#18
@coilysiren coilysiren mentioned this issue May 9, 2016
Closed
@coilysiren
Copy link
Contributor

This issue was moved to rubygems/bundler#4553

@segiddins segiddins mentioned this issue Jun 14, 2017
Merged
bundlerbot added a commit to rubygems/bundler that referenced this issue Jun 15, 2017
@bundlerbot
Auto merge of #5722 - bundler:seg-update-all-flag, r=indirect
08d1fa6 
Add `—all` flag to `bundle update`

### What was the end-user problem that led to this PR?

The problem was that some users would think they needed to run `bundle update` instead of `bundle install`, and we want such a (potentially) destructive action to require more explicit user approval.

### Was was your diagnosis of the problem?

My diagnosis was that `bundle update` shouldn't implicitly update _everything_ without an acknowledgement that it will do so.

### What is your fix for the problem, implemented in this PR?

My fix, based on #2646, it to require `bundle update --all` for the current `bundle update` behavior.

### Why did you choose this fix out of the possible options?

I chose this fix because it was already on 2-0-dev, courtesy of rubygems/bundler-features#18.
@deivid-rodriguez deivid-rodriguez mentioned this issue Mar 3, 2019
Closed
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
in progress incompatible ui
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@indirect @xaviershay @jlsuttles @coilysiren