-
-
Notifications
You must be signed in to change notification settings - Fork 221
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
Ignore paths #8
Ignore paths #8
Conversation
@@ -1,4 +1,4 @@ | |||
language: node_js | |||
node_js: | |||
- '0.10' | |||
- '0.8' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
out with the old, in with the new!
I'd like to publish an update to npm-check that will require the changes from this PR. If these changes were more than you were expecting and you don't want to accept them because the code is too different I totally understand. If that's the case, would it be okay if I use my PR to create a new module? I'll give you credit as the original author in the readme and code. |
Sorry, for the delay :( |
I just published the 0.4.0 version on npm with your changes. Once again, sorry it took me so long to merge this one. |
Awesome, no worries! Many thanks! |
did it on the plane, changed a bunch of stuff (sorry!), should be working, tests pass. plane is landing now so i have to stop.