Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Return error if any linter fails to run #2471

Merged
merged 3 commits into from Jan 15, 2022
Merged

Return error if any linter fails to run #2471

merged 3 commits into from Jan 15, 2022

Commits on Jan 10, 2022

  1. Return error if any linter fails to run 

    If a linter fails to run, store its name and use that to create a list
of all linters that failed to run. This will make `golangci-lint` exit
with a non-zero exit code if one or more linters fails but still ensure
all linters are run before exiting.
    @bombsimon
    bombsimon committed Jan 10, 2022
    Copy the full SHA
    9464bf5 View commit details
    Browse the repository at this point in the history

  2. Use string concatenation to construct error

    @bombsimon
    bombsimon committed Jan 10, 2022
    Copy the full SHA
    610f49e View commit details
    Browse the repository at this point in the history

Commits on Jan 14, 2022

  1. Use multierror instead of list of strings

    @bombsimon
    bombsimon committed Jan 14, 2022
    Copy the full SHA
    84d3c8f View commit details
    Browse the repository at this point in the history