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.

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

runner: non-zero exit code when a linter produces a panic #1979

Merged
merged 1 commit into from May 13, 2021
Merged

runner: non-zero exit code when a linter produces a panic #1979

merged 1 commit into from May 13, 2021

Conversation

ldez
Copy link
Member

@ldez ldez commented May 13, 2021

Fixes #1974

@ldez ldez added the bug Something isn't working label May 13, 2021
@ldez ldez merged commit 625445b into golangci:master May 13, 2021
@ldez ldez deleted the fix/exit-code-panic branch May 13, 2021 21:49
SeigeC pushed a commit to SeigeC/golangci-lint that referenced this pull request Apr 4, 2023
@ldez @SeigeC
runner: non-zero exit code when a linter produces a panic (golangci#1979
b00b901 
)
@ldez ldez added this to the v1.40 milestone Mar 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@butuzov butuzov butuzov approved these changes

Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
v1.40
Development

Successfully merging this pull request may close these issues.

panic in a linter should lead to a non-zero return code
2 participants
@ldez @butuzov