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 standard.
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 98.694% when pulling efe18a90e37c9b78b9c521bddcdb73f029bb392c on greenkeeper-standard-10.0.2 into e9f2f30d8cc5e740f7b4a48e88acdda0ac08a58b on master.
Coverage remained the same at 98.694% when pulling efe18a90e37c9b78b9c521bddcdb73f029bb392c on greenkeeper-standard-10.0.2 into e9f2f30d8cc5e740f7b4a48e88acdda0ac08a58b on master.
Hello lovely humans,
standard just published its new version 10.0.2.
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 standard. 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 239 commits .
8b43d45
authors
b002f41
10.0.2
f1f772a
changelog
9994f1d
code>eslint-config-standard@10.2.1</code8aa90ea
Merge pull request #858 from feross/feross/flow
1e66bdf
Merge pull request #851 from feross/readme-vim-ale
e0bdcdc
Update README.md
3c64877
readme: Add more specific Flow instructions
5126e74
Merge pull request #855 from pablopunk/patch-1
99b9e76
Fix list indentation
1366340
Merge pull request #854 from wayou/improve-translation
f737f22
📖 Spanish docs fixes
4b9ad60
improve readme translation for simplified chinese, fix typos
c7500e2
Readme: add mentions of neomake and syntastic
d60d2de
Update README.md
There are 239 commits in total. See the full diff.
Screencast
Try it today. Free for private repositories during beta.