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.

Sign up for GitHub

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

Jump to bottom

Use tools from paver.easy instead of our own functions. #13

Open

seanfisk opened this issue Jun 28, 2013 · 0 comments

Owner

seanfisk commented Jun 28, 2013

Check out paver.easy. Specifically, we should wrap our destructive commands in dry() and print using error(), info(), and debug().

Not sure if we should use sh() at this point since it runs it through the shell, which is almost never necessary and often a bad idea.

The text was updated successfully, but these errors were encountered:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment