Skip to content

Gitlab / CodeClimate report #2858

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
lschneiderbauer opened this issue May 30, 2025 · 3 comments
Open

Gitlab / CodeClimate report #2858

lschneiderbauer opened this issue May 30, 2025 · 3 comments

Comments

@lschneiderbauer
Copy link

Gitlab supports the consumption of a so called "codequality report" artifact, so that it can display static code checker results in a structured way, e.g. in merge requests, see https://docs.gitlab.com/ci/testing/code_quality/#import-code-quality-results-from-a-cicd-job.

This reports needs to be in a specific JSON format which is a subset of the CodeClimate format.

Linter like

already support that format.

Would you be interested in a contribution that adds support in the form of a function that consumes an "lints" object and returns a JSON string in the mentioned format?

@MichaelChirico
Copy link
Collaborator

makes sense. we already have something similar:

https://lintr.r-lib.org/reference/sarif_output.html

@lschneiderbauer
Copy link
Author

Thanks for the reference.
I presume the new function should behave in the same way, i.e. writing the result directly to a file instead of simply returning the json string?

@MichaelChirico
Copy link
Collaborator

I think it depends on what would work best for the tooling, so I leave that up to you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants