-
Updated
Apr 17, 2022 - Swift
Code quality
Automate your code review with style, quality, security, and test‑coverage checks when you need them most. Code quality is intended to keep complexity down and runtime up.
Here are 545 public repositories matching this topic...
-
Updated
Apr 14, 2022 - OCaml
-
Updated
Apr 16, 2022 - Rust
-
Updated
Apr 17, 2022 - Java
-
Updated
Apr 16, 2022 - JavaScript
-
Updated
Apr 16, 2022 - OCaml
Expected Behavior
When an exception is thrown while running a Rule we should provide information about the file and the Rule.
Current Behavior
We only provide information about the file.
Context
We had some issues lately where the users report exceptions on a Rule but we need to ask for the full stacktrace to know what's going on (an example: #4612). And the issue is also "de
We have a problem: if files aren't loaded/required we don't have branch data. If they are added through track_files we give it 0/0 branches which we show as 100% coverage (all possible branches are covered).
That math is "wrong" though here because there are branches but we don't know what they are. We should probably count total branches here as "unkown" and establish that in our "math unive
-
Updated
Apr 15, 2022 - JavaScript
W0402 (deprecated-module) error message says "Uses of a deprecated module 'optparse'".
I think it should say "Use of a deprecated module 'optparse'" instead of "Uses". Either "Use", or "Usage". "Uses" seems grammatically incorrect to me. What do you think?
Affects PMD Version:
6.17
Rule:
All rulesets.
Description:
PMD output does not inform the user as to the number of rules contravened while running the tool. The user has to look at the output file.
Code Sample demonstrating the issue:
Sep 01, 2019 9:42:45 AM net.sourceforge.pmd.cache.FileAnalysisCache loadFromFile
INFO: Analysis cache loaded
Sep 01, 2019 9:
-
Updated
Apr 15, 2022 - PHP
-
Updated
Apr 11, 2022 - JavaScript
-
Updated
Apr 13, 2022 - TypeScript
-
Updated
Apr 13, 2022 - Ruby
-
Updated
Feb 19, 2022
Piranha transforms:
someConsumer.accept((x) -> {
if(exp.isTreated(STALE_FLAG)){
doSomething(x);
}
else{
domeSomethingElse(x);
}
This bug: https://bugs.python.org/issue46175
We need to require super(cls, self) in this case.
-
Updated
Apr 7, 2022 - JavaScript
-
Updated
Oct 5, 2021 - TypeScript
-
Updated
Apr 15, 2022 - Python
-
Updated
Apr 13, 2022 - Makefile
I understand that optimisation of image/x-icon files has been added to Magick.NET (dlemstra/Magick.NET@c5e41c5). Are there any chances of this being added to Imgbot?
This has been requested before in #444, unfortunately, that issue has become stale without any comments whatsoever.
-
Updated
May 28, 2020 - Haskell
-
Updated
Apr 14, 2022 - TypeScript
-
Updated
Apr 14, 2022 - PHP
-
Updated
Jan 7, 2021 - Shell
Code quality apps
Datree
Policy enforcement solution for confident and compliant code
CodeFactor
Automated code review for GitHub
Sider
Automatically analyze pull request against custom per-project rulesets and best practices
Code Climate
Automated code review for technical debt and test coverage
Coveralls
Ensure that new code is fully covered, and see coverage trends emerge. Works with any CI service
LGTM
Find and prevent zero-days and other critical bugs, with customizable alerts and automated code review
Code Review Doctor
Python and Django code review tool that offers the fix right inside your PR
CodeScene
A quality visualization tool to identify and prioritize technical debt and evaluate your organizational efficiency
Codiga
Automate code reviews, analyze and scan code at each push/pull request
Codecov | Code Coverage
Automatic test report merging for all CI and languages into a single code coverage report directly into your pull request
TestQuality
The #1 Test Case Creation and Management for GitHub Workflows
Codacy
Automated code reviews to help developers ship better software, faster
Sonatype Lift
Lift helps you find and fix your most elusive bugs so you can spend time writing great code, not debugging it
Imgbot
A GitHub app that optimizes your images
CommitCheck
CommitCheck ensures your commit messages are consistent and contain all required information
Many repositories need to fix, so please help if you like.
If you could help, it would be helpful if you could comment before starting the work not to overlapping.
Fix example
Run exit command after lint.