-
Notifications
You must be signed in to change notification settings - Fork 9
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
workflow update #128
Comments
Should we move to ~ dependencies and make this run And concerning packaging for this and future commands, we have a few options:
I'm leaning towards (3) and the possibility of extracting |
I don't understand what the benefits of separating workflow-cmd into different packages vs files in the workflow-cmd package. Can you elaborate? |
Don't think it will give us the overview and make it possible to ask the question. I was thinking, maybe see if we can use npm-check-updates or something like a library. |
Maybe just an old habit to separate things, but as you say, there are not any real benefits for doing so at this point.
Sure, I was thinking of doing |
It would be nice to be able to update all workflow packages in workflow home with a simple command.
The text was updated successfully, but these errors were encountered: