-
Notifications
You must be signed in to change notification settings - Fork 22
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
force = true? #2
Comments
It's to prevent grunt from crashing on you when running long-lived tasks. Grunt aborts and manually stops the process when an error occurs, and this is not what you want when running it inside gulp. |
Ok, thanks. |
Why is this not a configurable option? I would like for my gulp task to fail when my grunt task fails.. |
Just got bitten bad by this horrible choice today. I regret ever deciding to go the plugin route instead of chaining via |
Hi, just wondering why you're setting force to true for all tasks. Is this necessary? It seems like it has the potential to be dangerous and I wonder if there was a reason to do that rather than parameterize it.
The text was updated successfully, but these errors were encountered: