static-analysis

Describe the bug
When using Semgrep in CI, the warning that Semgrep collects metrics is always visible. Even if the metrics are explicitely turned off and a local config file is used, the warning always pollutes the output.

Screenshots

**What is the priority of the bug to y

Many repositories need to fix, so please help if you like.

If you could help, it would be helpful if you could comment before starting the work not to overlapping.

Fix example

Run exit command after lint.

echo '::group:: Running golangci-lint with reviewdog 🐶 ...'
go

Oh, I thought I already added negative-int but I guess not. It should be easy to do if someone wants to add that

Originally posted by @orklah in vimeo/psalm#8060 (comment)

Should be trivial to add in Atomic::create (see how positive-int is handled there).

We'll probably want

• non-negative-int
• negative-int
• non-positive-int

just

Context

BooleanPropertyNaming considers naming of properties, while technically these const vals are properties, they also have a different naming convention and I have a feeling they rarely start with IS_ prefix.

Expected Behavior of the rule

I propose to exclude const from this check fully.

object WidgetPreferences { // Detekt: or a companion object

	/**
	 * Us