This repository has been archived by the owner on Apr 14, 2021. It is now read-only.
Bundle clean --dry-run should print listing without --force when no path is set #5027
Comments
|
I'm working on a PR for this. |
|
Done, see PR #5053. |
homu
added a commit
that referenced
this issue
Oct 10, 2016
Changed the behavior of 'bundle clean --dry-run' to output the list regardless of path set or force option Changed the behavior of 'bundle clean --dry-run' to output the list of gems bundle without having the local path set or providing the '--force' option. This change does not affect the actual behavior of 'bundle clean' which requires either the path being set or use of '--force'. Closes #5027.
homu
added a commit
that referenced
this issue
Oct 14, 2016
Changed the behavior of 'bundle clean --dry-run' to output the list regardless of path set or force option Changed the behavior of 'bundle clean --dry-run' to output the list of gems bundle without having the local path set or providing the '--force' option. This change does not affect the actual behavior of 'bundle clean' which requires either the path being set or use of '--force'. Closes #5027.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Currently if
pathis not set,bundle clean --dry-runrequires--forceto print listing. It would be nice if it bundler followed the common paradigms where--dry-runprints a listing of what changes without--force, and--forceis only required when you're prevented from executing the action for some reason and you need to override the failsafes and force the action.Propose change current
bundle clean --dry-run --forcetobundle clean --dry-runfor the case whenpathis not set.The text was updated successfully, but these errors were encountered: