Inspired by super-linter by GitHub, but using Powershell.

Improvements

• Powershell 7 Runner Script
• Linters run independently, a failure in one won't impact others
• Linters are defined as structured objects
• Configuration System for Linters
• Problem Matcher and Github Annotations Support
• Linter Plugin Support
• Linters run in parallel for huge performance increase
• Files to lint are evaluated prior to run, better performance
• Linter Results are posted as annotations to the action, where possible
• Linters that can process multiple files at once are supported, e.g. for static type checking
• Supports Github Actions Inputs
• Provides a JSON representation of the results as an output

Linter States

Linters have one of two states, usually determined by their exit code but also can be determined by output:

1. Failure: The linter itself had an unrecoverable error, such as bad configuration
2. Success: The linter completed and no issues were found

Linter Suggestions

A linter may emit nothing at all or it may emit suggestions. Those suggestions can fall into one of the following categories:

1. Error: The linter determined an error that will likely prevent the code from functioning correctly
2. Warning: The linter found something that isn't necessarily an issue but has the potential to cause one
3. Info: The linter has a suggestion or refactoring option to improve compatibility/performance/etc.