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 coveralls.
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.
With Integrationsfirst-class bot support landed on GitHub and we’ve rewritten Greenkeeper to take full advantage of it. Simpler setup, fewer pull-requests, faster than ever.
Screencast Try it today. Free for private repositories during beta.
Coverage remained the same at 100.0% when pulling ec05ccf6663e9e3885597768837e4f2e4a511ae6 on greenkeeper-coveralls-2.11.16 into c5ea3070b422a65a4df1dc13fd3494b3d35beedd on master.
Coverage remained the same at 100.0% when pulling ec05ccf6663e9e3885597768837e4f2e4a511ae6 on greenkeeper-coveralls-2.11.16 into c5ea3070b422a65a4df1dc13fd3494b3d35beedd on master.
Coverage remained the same at 100.0% when pulling ec05ccf6663e9e3885597768837e4f2e4a511ae6 on greenkeeper-coveralls-2.11.16 into c5ea3070b422a65a4df1dc13fd3494b3d35beedd on master.
Hello lovely humans,
coveralls just published its new version 2.11.16.
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 coveralls. 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 13 commits .
8dfcfd6
version bump
4bc93ac
Merge branch 'master' of github.com:nickmerwin/node-coveralls
671acca
removed codeship badge
f390392
Merge pull request #152 from ndaidong/master
de968b0
Merge pull request #147 from hyperlink/update-request-dep
72a4046
Merge pull request #154 from a0viedo/patch-1
87b27f7
Merge pull request #142 from Hirse/feature/travis-pr
3edbecb
Merge pull request #155 from kasperlewau/master
d117e3d
reenable drone
dd230f6
don't hardcode minor version
cc0882d
Update outdate dependencies
99edf1a
Fix node-uuid deprecation by updating request dependency
f94b647
Get PR number from TRAVIS
See the full diff.
Screencast
Try it today. Free for private repositories during beta.