-
-
Notifications
You must be signed in to change notification settings - Fork 16
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
Recursive Updater ? #5
Comments
Thanks! Sorry I just saw this issue.
I did this locally. I created an updater that runs all the updaters on a directory of projects.
We could add support for that. Currently you can define the updaters on the {
"update": {
"updaters": ["license", "gitignore"]
}
}
I was thinking about this for a while. These are my proposed solutions:
|
Yes, that sounds as a good plan. |
ping @jonschlinkert any updates on this? |
I do indeed have an update :) I created an updater to do this a while ago and wanted to spend some time testing it out. I also created a similar project for I have a lot on my plate at the moment, but I'll try to push it up as soon as I get a chance. |
Sounds encouraging! |
Absolutely fantastic project, can stop using it to consolidate all my projects!!!
One idea I was thinking of:
update --recursive
and the based on the current directory all updaters defined in each of the projects would be appliedI started to prototype that a bit and this is what I was actually seeking for for quite some time.
What are your thoughts?
The text was updated successfully, but these errors were encountered: