coveralls
commented
8 years ago Coverage remained the same at 98.606% when pulling 311c5e4efb8f471a372d3858607121c02f08d1a1 on greenkeeper-watch-1.0.0 into e5202755bcb65f007a7db095cf382cadb15cbdae on master.
Hello lovely humans,
watch just published its new version 1.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 watch. 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 3 commits .
7ea86dd1.0.01546b010.19.35ac4690fix(watchTree): convert options.interval to seconds (#113)See the full diff.
This pull request was created by greenkeeper.io.
Tired of seeing this sponsor message? :zap:
greenkeeper upgrade