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

ci: improve golangci-lint output #254

Merged
merged 1 commit into from
Dec 28, 2022

Conversation

oleg-jukovec
Copy link
Collaborator

@oleg-jukovec oleg-jukovec commented Dec 27, 2022

The patch adds a second golangci-lint run that prints errors in human-readable format [1].

  1. github action log output doesn't print the affected file name & line golangci/golangci-lint-action#119

Closes #231

The first run of golangci-lint prints errors in GitHub Actions format:
1

The second run in human-readable format:

2

Unfortunately, it doesn't work in one run and we need two different ones.

@oleg-jukovec oleg-jukovec force-pushed the oleg-jukovec/gh-231-golint-ci-output branch 2 times, most recently from 8a8b557 to 25973fd Compare December 27, 2022 11:03
The patch adds a second golangci-lint run that prints errors in
human-readable format [1].

1. golangci/golangci-lint-action#119

Closes #231
@oleg-jukovec oleg-jukovec merged commit 7a593cc into master Dec 28, 2022
@oleg-jukovec oleg-jukovec deleted the oleg-jukovec/gh-231-golint-ci-output branch December 28, 2022 08:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

golint does not print backtrace
3 participants