super-linter | multiple linters to install as a GitHub Action | Code Analyzer library

by github Shell Version: v5.0.0 License: MIT

X-Ray Key Features Code Snippets Community Discussions(3)Vulnerabilities Install Support

kandi X-RAY | super-linter Summary

super-linter is a Shell library typically used in Code Quality, Code Analyzer applications. super-linter has no bugs, it has no vulnerabilities, it has a Permissive License and it has medium support. You can download it from GitHub.

This repository is for the GitHub Action to run a Super-Linter. It is a simple combination of various linters, written in bash, to help validate your source code.

Support

Quality

Security

License

Reuse

Support

super-linter has a medium active ecosystem.

It has 8690 star(s) with 1004 fork(s). There are 315 watchers for this library.

It had no major release in the last 12 months.

There are 36 open issues and 914 have been closed. On average issues are closed in 63 days. There are 36 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of super-linter is v5.0.0

Quality

super-linter has 0 bugs and 0 code smells.

Security

super-linter has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

super-linter code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

super-linter is licensed under the MIT License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

super-linter releases are available to install and integrate.

Installation instructions are not available. Examples and code snippets are available.

It has 460 lines of code, 0 functions and 5 files.

It has low code complexity. Code complexity directly impacts maintainability of the code.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of super-linter

Get all kandi verified functions for this library.

super-linter Key Features

No Key Features are available at this moment for super-linter.

super-linter Examples and Code Snippets

No Code Snippets are available at this moment for super-linter.

Community Discussions

Trending Discussions on super-linter

Validate .editorconfig file using Github Action

Make the build failure when code coverage is less than x%

How can I satisfy shellcheck without causing script failure?

QUESTION

Validate .editorconfig file using Github Action

Asked 2021-Jun-06 at 23:48

I want to make sure that any pull request in my Github repo follows the rules defined in .editorconfig (ASp.NET Core 5 C# project). I have found https://github.com/github/super-linter to lint the code using,

I have added the below linter.yml file in my workflow,

...

ANSWER

Answered 2021-Jun-06 at 23:48

Checking the Environment Variables from the Super Linter Github Action, the default value for the EDITORCONFIG_FILE_NAME file is .ecrc.

Therefore, if your file's name is .editorconfig you'll have to add it to the action arguments list with something like:

Source https://stackoverflow.com/questions/67863002

QUESTION

Make the build failure when code coverage is less than x%

Asked 2021-Mar-21 at 06:49

I'm working with github actions and in my tests I need to make myt build fail when my code coverage percentage is less than 80%. I looked up some github actions in github marketplace but dont find anything. Can I do it ? I'm linking my workflow file if it migth help

...

ANSWER

Answered 2021-Mar-21 at 06:49

I would replace invocation of go test with an invocation of a shell script as explained here.

The shell script would look something like this

Source https://stackoverflow.com/questions/66246460

QUESTION

How can I satisfy shellcheck without causing script failure?

Asked 2021-Feb-06 at 00:12

I am currently testing out GitHub Actions and the quickstart explains how to add super-linter to a repo which is an easy way to apply linting across a whole repo - I like this idea so I have added it to my repo, one of the linters it applies is shellcheck and it has thrown up some errors on one of my shell scripts.

That shell script issues docker run using the following code:

...

ANSWER

Answered 2021-Feb-05 at 23:15

Looks like the man page https://www.mankier.com/1/shellcheck describes ways to override errors.

Ignore certain errors:

Source https://stackoverflow.com/questions/66071810

Community Discussions, Code Snippets contain sources that include Stack Exchange Network