-
Notifications
You must be signed in to change notification settings - Fork 33
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
wishlist: add a "what I plan to do" mode to show what would change #81
Comments
This should be pretty straight-forward to implement. The only problem is that Would you be open for a PR? :) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It would be nice to get a preview of what
updtr
is planning before letting it give it a shot, for my workflow; I can usenpm outdated
to get what I expect to be the same information, but I have not inspected the code ofupdtr
to verify that this will necessarily always be correct.I am not thinking "run the tests with the update, but do not commit it", but rather, "show what will be tried." The attempt may, of course, fail, and lead to the normal handling of test failures after update, which may vary from the plan.
I am thinking of a display specifically of something like:
You, uh, might want to find someone more competent at naming things than me to work out what the flag should be called, though. :)
The text was updated successfully, but these errors were encountered: