linter

~/code/rubocop$ grep -iro "autocorrect" . | wc -l
    1971
~/code/rubocop$ grep -iro "auto-correct" . | wc -l
    1551

Both autocorrect and auto-correct are used frequently in RuboCop. Should we be consistent? If so, which one?

Any change should only affect comments and other string content, not method names.

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 of the rule

UnnecessaryAbstractClass should have a concise description like other rules

Context

I just updated Detekt 1.19.0 to 1.20.0 and got this failure:
https://github.com/TWiStErRob/net.twisterrob.cinema/security/code-scanning/227

The message is just plain weird to be this long:
![image](https://user-images.githubusercontent.com/2906988/164910306-4b4478c4-0

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

Current problem

According to PEP8, exception class names should end with "Error" if they define an actual exception.
However, pylint doesn't offer such an check.

Desired solution

Add a new naming check which checks if a class extends any known exception class. Then check it's name. Since an exception can also be used as a non-error offer a configuration like a "allow-list" similar to g

Affects PMD Version:

6.45.0

Description:

UseCollectionIsEmptyRule fails with NPE if:

1. object under test is declared as re

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.