Update danger to the latest version 🚀#1393
Merged
Conversation
Codecov Report
@@ Coverage Diff @@
## master #1393 +/- ##
=======================================
Coverage 14.35% 14.35%
=======================================
Files 201 201
Lines 4613 4613
Branches 506 513 +7
=======================================
Hits 662 662
+ Misses 3510 3499 -11
- Partials 441 452 +11
Continue to review full report at Codecov.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Version 1.0.0 of danger just got published.
The version 1.0.0 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 danger.
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.
Commits
The new version differs by 16 commits.
a6223c1Merge pull request #301 from danger/v11a80321Prepare for v1.0 🎉55c7eb5ci(travis): build on Node 8 (#300)c5f76a3Merge pull request #297 from danger/remove_getting_starteda0c9bddMerge master8ad165fFix code syntax inside the node app tutorial022a12fRemove the getting started docs09dcbd7Merge pull request #295 from danger/readme_tweaks43b6898Add information about codeship classic for docs423df13Clean up Jenkins doc formatting and URLs45c727cCreates inline docs for all providers61686afMerge pull request #293 from danger/readme_tweaks338bc88README tweaksc54e803README tweaksfdae482Merge pull request #292 from danger/vision_2There are 16 commits in total.
See the full diff
Not sure how things should work exactly?
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot 🌴