-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make --dry-run flag consistent across rubygems commands #3867
Conversation
GNU make also provides |
@bronzdoc on master, |
I agree with @duckinator! |
@bronzdoc Do you agree with @duckinator's suggestion? Are you planning to update the PR with that approach? |
Dang, I totally forgot about this... I agree! Will Work on Rubygems later today and will update this PR sorry for taking that long fellas |
aedc55b
to
addc644
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I saw that the --update-sources
option to gem install
passes a :Deprecated
first argument to add_option
and the consequence of this is that the option appears under a separate group called Deprecated Options
in gem install --help
output. Maybe it's a good idea to do it here too?
Should I deprecate |
Not sure 🤔. I think we can leave it as it is, and remove it if it confuses someone, but I don't have an issue with deprecating it either. |
Ok, sounds good |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks good to me!
181e83b
to
38230a7
Compare
Make --dry-run flag consistent across rubygems commands
Description:
closes #3866
Make
--dryrun
flag consistent across Rubygems commandsI will abide by the code of conduct.