Update codacy-coverage to version 2.0.2 🚀 #23
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
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,
codacy-coverage just published its new version 2.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 codacy-coverage.
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!
🌴
GitHub Release
Feature
Add support for automatic detection of report languages.
If you do not explicitly pass the language the tool will partition your files by language and send separate reports for each automatically.
Supported languages: Javascript [.js, .jsx], Typescript [.ts, .tsx] and Coffeescript [.coffee].
The new version differs by 45 commits .
0ee0002Release version 2.0.2749f3f4Merge pull request #41 from codacy/detect-files-languagec31dadfDetect files language and send separate reports per language8b149e6Merge pull request #40 from lapa182/patch-1efd669aFix markdown typo issue6f71931Add language docs3cff062Release version 2.0.193b586eMerge pull request #37 from codacy/feature/languageParam2fe48bd6Fix lintersee1b86cAllow to pass a language other than Javascript as paramb991fe3Merge pull request #34 from codacy/ci42a516eRun test on windowsc9b290eMerge pull request #32 from codacy/update-readme9d66ca4Fix enterprise url info64588aeMerge pull request #31 from cog/patch-1There are 45 commits in total. See the full diff.
Screencast
Try it today. Free for private repositories during beta.