-
Notifications
You must be signed in to change notification settings - Fork 29
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
Feature suggestion: Create separate commits per upgraded package #37
Comments
Thanks!
It's an interesting feature but it doesn't replicate the way I upgrade modules in my projects - I do it in one run so I don't think it will be useful for me. Let's see if this issue collects a noticeable amount of "thumb up"s I'll be happy to review and merge your PR.
Just check existence of the corresponding file in the project?
Here is the flow I would use:
|
Alright, thanks for the reply. I'll improve my PoC and create a PR of it whenever I have some time. |
This sounds like a useful feature! I'd never be patient enough to do the splitting by hand, but sure would appreciate the separate commits when e.g. bisecting after discovering something broke later. |
Hello, thanks for an amazing tool.
I want to update packages with separate commits (including lockfile) per package and I recently started working on a PoC for that feature in a fork.
However, I thought you might actually find this feature useful because it's such a tiny addition.
My PoC that works assuming
yarn
:master...olpeh:5897e9f68c5d6d4d1d4f3afccdd0ba7579e82f95
What do you think about this?
If this is something that sounds useful, I can try to improve this PoC and create a PR about it.
Some things to be solved though:
yarn.lock
orpackage-lock.json
exists?The text was updated successfully, but these errors were encountered: