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 gulp-jscs.
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.
Coverage remained the same at 100.0% when pulling 2ddc04344d49106c905dde6d0dc22a02e21aa3e5 on greenkeeper-gulp-jscs-4.0.0 into a10d7ce1717025820536c4c101e80951517bb89c on master.
Coverage remained the same at 100.0% when pulling ec622637fb81500eb577c7058672c4fa0b737317 on greenkeeper-gulp-jscs-4.0.0 into e62f2416c1f02ef614561f621359e4f4a88e07fa on master.
Coverage remained the same at 100.0% when pulling cf58e913614ad4eba5abbaed0ec385ef6e28080e on greenkeeper-gulp-jscs-4.0.0 into 6619b24eebbb9ed3b3ceabd4e1fdae77f39b3c27 on master.
Coverage remained the same at 100.0% when pulling 333ca75925400999467796f97783ead86dd67c6b on greenkeeper-gulp-jscs-4.0.0 into da9e3af75e70a49a7c87d8f413e7d6c4afc546fa on master.
Coverage increased (+87.7%) to 100.0% when pulling 7ff89f744b70b1287eaa0c84890dd53056afd700 on greenkeeper-gulp-jscs-4.0.0 into 1ece4637793913578ff7e5f18f85b9dad4cfb97d on master.
Coverage remained the same at 100.0% when pulling 782c9f11e8345af3a423d4107e605a1511ae369e on greenkeeper-gulp-jscs-4.0.0 into f6874ac3205d3fe7bc2503c57fd2f0e64eb5950e on master.
Coverage remained the same at 12.281% when pulling f6d080b2cfb0207c27d7b96db0cbbdd310d745a9 on greenkeeper-gulp-jscs-4.0.0 into 1ad2eb83b051adad640d24b13370c376eb0eb624 on master.
Hello lovely humans,
gulp-jscs just published its new version 4.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 gulp-jscs. 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:
GitHub Release
Upgrade to JSCS 3.
The new version differs by 3 commits .
f7471e8
4.0.0
7face69
deps: jscs@3.0.4 (#112)
376e2dc
bump dev deps
See the full diff.
This pull request was created by greenkeeper.io.
Tired of seeing this sponsor message? :zap:
greenkeeper upgrade