# Share a Pylint HTML Report — A Link Instead of 4,000 Console Lines

Canonical: https://commareports.com/share-pylint-report
Published: 2026-08-31

> pylint --output-format=json piped through pylint-json2html gives you a browsable report. Publish it to Comma so the cleanup conversation happens on the findings.

# Share a Pylint HTML report

The first time you run Pylint against an inherited Python codebase it prints
several thousand lines and everybody agrees to deal with it later. Later never
arrives, partly because there is no artifact to point at — just a command
whose output scrolls off.

## Produce the page

```bash
pip install pylint pylint-json2html

pylint mypkg --output-format=json > pylint.json || true
pylint-json2html -f json -o pylint.html pylint.json
```

The `|| true` is deliberate: Pylint returns a bitmask exit code (fatal, error,
warning, refactor, convention), so any finding at all makes the command
"fail". You want the report either way.

## Publish it

Drag `pylint.html` into [the app](https://commareports.com/), or from CI:

```bash
curl -fsS -X PATCH "https://commareports.com/api/v1/reports/$REPORT_ID" \
  -H "Authorization: Bearer $COMMA_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d "$(jq -n --rawfile html pylint.html \
        --arg title "Pylint — $(git rev-parse --short HEAD)" \
        '{title: $title, html: $html}')"
```

The generated page is self-contained, so there is nothing else to upload.

PATCH the same report id every run: one URL, a revision per run, and lint debt
that goes down becomes a chart rather than an assertion.

## Make the cleanup collaborative

A lint backlog is only ever cleared by someone claiming a slice of it. That is
what the anchored threads are for:

- A thread on the `too-many-locals` cluster in `etl/` — "mine, this week".
- A thread on a rule you intend to disable rather than fix, with the reason
  recorded next to the rule instead of in a `# pylint: disable` comment that
  says nothing about why.

See [commenting on HTML](/comment-on-html).

## Scheduling it

Lint reports are the natural case for a
[routine](/features/routines/scheduled-html-reports): re-run weekly against
`main`, PATCH the same report, and the trend maintains itself. Nobody has to
remember to regenerate anything.

## Limits

- **Entry HTML: 5 MB.** A very large first-run report can approach that —
  filter to errors and warnings (`--disable=C,R`) for the shareable view and
  keep the full JSON in CI.
- Assets: 25 MB per file, 250 MB and 500 files total.
- **60 requests/minute per token.**

## Try it

Comma is free — unlimited reports, unlimited commenters, unlimited revision
history.

**[Publish a lint report →](https://commareports.com/)**

### Related

- [Share a Ruff report](/share-ruff-report) · [Share an ESLint report](/share-eslint-report)
- [Share a Bandit report](/share-bandit-report) · [Share a RuboCop report](/share-rubocop-report)
- [Scheduled reports](/features/routines/scheduled-html-reports) · [Publish from CI](/docs/ci)