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 qunitjs.
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 181 commits (ahead by 181, behind by 1).
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.
Hello lovely humans,
qunitjs just published its new version 2.3.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 qunitjs. 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 181 commits (ahead by 181, behind by 1).
75d9fde2.3.0d43378fBuild: Prepare 2.3.0 release, including authors and history updateb1646e7Core: Test#pushFailure now calls Test#pushResult73999cbHTML Reporter: Display todo tests on hidepassedec2a36fCLI: Add support for custom reporters3a9d983CLI: Properly support aborting and restarting testsdad4177CLI: Add file watching option51e4382Core: Revamp processing order to one test at a timec4f3a96Core: Remove parameter from ProcessingQueue#advance098f063CLI: Add description to help command86b74a4CLI: Add seed option41cb625Core: Account for validity of test in test countsf2f82e5CLI: Support filtering testsfaae7a0Core: Extract processing logic into ProcessingQueuec65a374Tests: Add CLI testsThere are 181 commits in total. See the full diff.
Screencast
Try it today. Free for private repositories during beta.