DocsCustomize Solemly
Controlling Noise
How Solemly keeps reviews focused, and how to dismiss what you don't need.
Solemly is built to say less and be right more often. Here's what keeps reviews focused, and what you can do when a finding isn't useful.
Built in#
- Double-checked findings. Findings are checked again before they're posted, and ones Solemly can't back up are dropped.
- No nitpicks. Findings rated
NITare left out. - Focused on what matters. A large change gets its most important issues, not a wall of comments.
- Your rules first. Instruction files can say what not to comment on, such as formatting your formatter already enforces.
- Latest commit only. Reviews of older commits are dropped when you push again, so you don't get stale comments.
Files that aren't reviewed#
Some files are left out of every review, because they're generated or third-party:
| Left out | Examples |
|---|---|
| Lockfiles | package-lock.json, yarn.lock, pnpm-lock.yaml, poetry.lock, uv.lock, go.sum, Cargo.lock, Gemfile.lock, composer.lock and similar |
| Third-party and build directories | vendor/, third_party/, node_modules/, bower_components/, dist/, .next/, __pycache__/ |
| Minified code and source maps | *.min.js, *.min.css, *.js.map and other minified files |
| Test snapshots | __snapshots__/, *.snap |
| Binary files | Images, archives, fonts, media, compiled binaries, databases |
| Generated code | Files marked as generated, such as with an @generated header |
SVG files are reviewed, since they can contain script.
Dismiss a finding#
Reply @solemly ignore to a finding (in its thread on GitHub) to dismiss it. It won't be raised again on that pull request. See PR Commands.
Tell us about a bad finding#
If Solemly keeps getting something wrong, email support@solemly.com with the pull request link. We look at the exact diff and review that produced it.
Something missing or unclear? Tell us.