#2369·reviewdog

Nicer looking `diff` when using `github-pr-checks`?

Author: faximanCreated Dec 19, 2025Updated Aug 20, 2026

We are using github-pr-checks in a GitHub Action to report issues based on a diff generated by some linter tool, basically:

bash
git diff | reviewdog -name=goimports -f=diff -reporter=github-pr-checks -fail-level=error -filter-mode=nofilter

This works fine, except generated errors are very hard to decipher since they just print the raw diff output:

check-linters: acl.go#L46
[goimports] reported by reviewdog  Raw Output: acl.go:46:- actionView aclAction ="view" acl.go:45:+ actionView aclAction = "view"

(try to spot the actual problem...)

However, if I instead use github-pr-review, the review comments I get are super nicely formatted with a red/green diff. But our devs don't like this mode, since they perceive review comments as overly spammy (they trigger email notifications etc.)

Is it possible to get nicer errors based on -f=diff with github-pr-checks?