linter

There are some annoying warnings when building the documentation site:

$ antora --pull antora-playbook.yml
asciidoctor: WARNING: skipping reference to missing attribute: 1
asciidoctor: WARNING: skipping reference to missing attribute: 3
asciidoctor: WARNING: skipping reference to missing attribute: word
asciidoctor: WARNING: skipping reference to missing attribute: word
asciidoctor: W

Your feature request related to a problem? Please describe.

GoKart is a new stand-alone security-focused static analysis tool.

Describe the solution you'd like.

Add support for GoKart. It uses go/analysis.

Describe alternatives you've considered.

Run GoKart separately to golangci-lint.

Additional context.

_No respo

What steps are needed to reproduce the bug?

test.scss

$frames: ("one", "two", "three");

@each $name in $frames {
  @keyframes frame-#{$name} {
    /* CSS ... */
  }
}

$ npx stylelint test.scss

test.scss
 4:14  ✖  Expected keyframe name to be kebab-case  keyframes-name-pattern

The name is kebab case, but due to the string interpolation, the line is f

Describe the bug

git diff-tree used by linter on push checks only files from the last commit and regardless of files status, so deleted or renamed files are also checked.

There are now 2 different git commands used for finding the list of broken files (find them here: https://github.com/github/super-linter/blob/v3.14.4/lib/functions/buildFileList.sh#L59-L105). git diff-tree is u

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

Expected Behavior

Website renders HTML.

Observed Behavior

Steps to Reproduce

https://detekt.dev/docs/gettingstarted/type-resolution/#is-my-rule-using-type-resolution

Context

https://github.com/detekt/detekt/blob/7cb5d9603bf4bf1f263dc393764178ef8d1df8cf/website/doc

Describe the bug
A clear and concise description of what the bug is.

To Reproduce
Steps to reproduce the behavior:

1. create .bandit file with content:

[bandit]
tests: B101,B102,B301

2. run bandit -c .bandit -r module/
3. get error:
   [main] ERROR .bandit : Error parsing file.

Expected behavior
working as described in readme

Bandit version

ba

Bug description

The documentation states that "Constructor parameters can be documented in either the class docstring or the init docstring, but not both.

However, I see that the docstring is only recognized when in the class docstring.

Consider this simple `mai

Affects PMD Version: 6.42.0

Description:
In this Link, line 11 and li

Elm has the option to output errors as JSON (via a flag), and something like that is handy for writing tooling around it. I'm trying to integrate pytype into ALE and this would make it a lot easier.