This version is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of ghooks.
Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right?
Are you unsure about how things are supposed to work?
There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.
Good luck with your project :sparkles:
You rock!
:palm_tree:
The new version differs by 21 commits .
59b3aa3chore: drop support for Node.js 0.10 (#183)
Coverage remained the same at 100.0% when pulling cb97322cb3c24b967eb8ba8a64ff9608e46ceb0d on greenkeeper-ghooks-2.0.0 into 604bdee713700157d7ac0b9cb02274520a83bdbc on master.
Coverage remained the same at 100.0% when pulling cb97322cb3c24b967eb8ba8a64ff9608e46ceb0d on greenkeeper-ghooks-2.0.0 into 604bdee713700157d7ac0b9cb02274520a83bdbc on master.
Hello lovely humans,
ghooks just published its new version 2.0.0.
This version is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of ghooks. Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right? Are you unsure about how things are supposed to work?
There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.
Good luck with your project :sparkles:
You rock!
:palm_tree:
The new version differs by 21 commits .
59b3aa3
chore: drop support for Node.js 0.10 (#183)
9f95fbb
docs(readme): add deprecation note
6e601be
chore(package): update cz-conventional-changelog to version 1.2.0 (#157)
137a224
chore(package): update cz-conventional-changelog to version 1.1.7 (#150)
481536f
chore(package): update eslint-plugin-mocha to version 4.3.0 (#144)
86a0cde
chore(package): update mocha to version 3.0.0 (#141)
c858ccd
Merge pull request #126 from gtramontina/gtramontina/document-githooks-workdir
e64964e
docs(hooks): Add note about the hooks' working directory
7d2fa5a
chore(package): update nyc to version 7.0.0 (#124)
16d7a6f
Merge pull request #117 from gtramontina/gtramontina/appveyor
ae2be01
test(path): Provide process.{env,platform} to
getPathVar
bcfea36
test(paths): Resolve paths properly within tests
861a4c5
docs(build): Add Appveyor badge
b89a495
chore(build): Setup Appveyor
e3e552a
fix(hook): windows path escapes (#115)
There are 21 commits in total. See the full diff.
This pull request was created by greenkeeper.io.
Tired of seeing this sponsor message? :zap:
greenkeeper upgrade