Update coveralls to version 2.13.1 🚀 #164
Merged
Conversation
This file contains 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
jescalan
force-pushed
the
greenkeeper-coveralls-2.13.1
branch
2 times, most recently
from
d596380 to
870cfe9
Compare
|
Changes Unknown when pulling 870cfe9 on greenkeeper-coveralls-2.13.1 into ** on master**. |
jescalan
force-pushed
the
greenkeeper-coveralls-2.13.1
branch
from
870cfe9 to
dd90d66
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Hello lovely humans,
coveralls just published its new version 2.13.1.
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 ✨
You rock!
🌴
The new version differs by 7 commits .
b9032a1better Jenkins detection2821200version bumpef7e811Parse commit from packed refs if not available in refs dir. (#163)e476964Merge pull request #162 from evanjbowling/patch-163a7f92Update README.mdd571dacmerge, version bump1575050branching WIPSee the full diff.
Screencast
Try it today. Free for private repositories during beta.