GitLab-CQ
Parse linter output and convert it to GitLab Code Quality report.
Supported Linters
Pull Requests for additional linter support are welcome.
Installation
$ python -m pip install -U gitlab-cq
Or use pipx:
$ pipx install gitlab-cq
Usage
There are two ways to use GitLab-CQ: run linter command via. GitLab-CQ or parse linter output from stdin.
Run linter command via. GitLab-CQ:
$ gitlab-cq [--output file_path] [--merge] [--echo] CMD [Arguments]
Parse linter output from stdin:
$ CMD [Arguments] | gitlab-cq [--output file_path] [--merge] [--echo] LINTER
Arguments:
CMD:- Command to run linter.
Arguments:- Arguments for linter command.
LINTER:- Linter name to parse:
{ruff, pyright, mypy, gcc, clang-tidy, clang}
- Linter name to parse:
Options:
--output file_path:- Output to file_path.
--merge:- Merge output to existing JSON file (available if
--outputis specified).
- Merge output to existing JSON file (available if
--echo:- Echo linter output (available if
--outputis specified).
- Echo linter output (available if
Required options for linters
The following options are required for linters when parsing from stdin.
(No need to add the following when the linter runs via. GitLab-CQ, since these options are automatically added.)
ruff:--output-format jsonis required and do not pass--outputoption.
pyright:--outputjsonis required.
mypy:--output=jsonis required.
Example
Integration to GitLab CI and save an GitLab CQ artifact:
code quality:
stage: test
script:
# Run linters via. GitLab-CQ and merge output to gl-code-quality-report.json
- pipx install gitlab-cq
- gitlab-cq --output gl-code-quality-report.json ruff check .
- gitlab-cq --output gl-code-quality-report.json --merge pyright .
- gitlab-cq --output gl-code-quality-report.json --merge mypy .
# Parse linter/compiler output and merge to gl-code-quality-report.json
- gcc -Wall -Wextra -o /dev/null -c main.c 2>&1 | gitlab-cq --output gl-code-quality-report.json --merge gcc
- clang-tidy -format-style=file -p . --quiet main.c | gitlab-cq --output gl-code-quality-report.json --merge clang-tidy
artifacts:
reports:
codequality: gl-code-quality-report.json
Author
Yoshiki Matsuda (@yosh-matsuda)
Metadata
Release files for gitlab-cq 0.2.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| gitlab_cq-0.2.2.tar.gz | 14.0 kB | Without provenance | Details for gitlab_cq-0.2.2.tar.gz |
Release files / gitlab_cq-0.2.2.tar.gz
| Download URL | gitlab_cq-0.2.2.tar.gz |
|---|---|
| Size | 14.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d688c2aea85cdbb2293cbff3d074bdf26c4ea30c8b02cff23384011dac26c791
|
|
BLAKE2b-256 checksum How to use checksums |
447b28d62ca9cec9eececb1efb58e98c0cbd108d8939c30d76df06317e4e4901
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.12.5 {"installer":{"name":"uv","version":"0.12.5","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"26.04","id":"resolute","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Security for gitlab-cq 0.2.2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.