Skip to content
#

linter

Here are 1,749 public repositories matching this topic...

bbatsov
bbatsov commented Dec 2, 2020

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
documentation good first issue maintenance
golangci-lint
mykter
mykter commented Aug 19, 2021

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

enhancement good first issue linter: new
stylelint
webfrontzhifei
webfrontzhifei commented May 8, 2022

What steps are needed to reproduce the bug?

.demo{
position: absolute;
right: .0rem;
top: -.52rem;
}

What Stylelint configuration is needed to reproduce the bug?

const config = {
extends: ['stylelint-config-standard'],
plugins: ['stylelint-scss'],
rules: {}
};

module.exports = config;

How did you run Stylelint?

stylelint --fix

Which version of Stylelint

status: ready to implement type: bug good first issue
dec5e
dec5e commented Jan 28, 2021

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

bug good first issue help wanted O: backlog 🤖
reviewdog
TWiStErRob
TWiStErRob commented Apr 23, 2022

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

help wanted rules good first issue
davidak
davidak commented Jun 18, 2018

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

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

Expected behavior
working as described in readme

Bandit version

ba
bug good first issue
fischbacher
fischbacher commented May 9, 2022

Current problem

We sometimes see code like this:

def foo(*, left=None, right=None):
  """ ... """
  if (left is None) != (right is None):
    raise ValueError('Either both left= and right= need to be provided or none should.')

It is very easy to make the mistake of writing the check as:

def foo(*, left=None, right=None):
  """ ... """
  if left is No
Help Wanted 🙏 Proposal 📨 good first issue Optional Checkers

Improve this page

Add a description, image, and links to the linter topic page so that developers can more easily learn about it.

Curate this topic

Add this topic to your repo

To associate your repository with the linter topic, visit your repo's landing page and select "manage topics."

Learn more