Closed rigomate closed 1 week ago
The infer action gives such an overview of the issues, which it suspects:
If we run it in the CI where do we see the results? Your screenshot indicates it's somewhere on Github?
Also how is this different from codacy which we use in other repositories
It can be seen in the actions section at github: In my fork it is here: https://github.com/rigomate/java-ice-adapter/actions/runs/6855882675
I don't know how it differs codacy, but my philosophy is simple: use as many code checkers as possible. Maybe the will find some viable issue. I think this null pointer call which it found and is fixed in the pull request sets a good example, that this tool might find real issues.
Cheers!
Add infer static code analysis checker to builds. Solve one trivial possible null pointer dereferencing.