feat(gh-actions/go/code-sanity): Report the golangci-lint findings#110
Open
feat(gh-actions/go/code-sanity): Report the golangci-lint findings#110
Conversation
By default, the golangci-lint-action prints the output of the linter to the console, but hidden in a "run golangci-lint" group. We want the output to be visible without having to search for that group and click on it, so we write it to a file first and then log the content of that file in a subsequent step.
adombeck
force-pushed
the
print-golangci-lint-output
branch
from
65872d0 to
a1e329c
Compare
Contributor
Author
|
This is how it looks like now: https://github.com/canonical/authd/actions/runs/22155791310/job/64194317331?pr=1271#step:5:277 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
By default, the golangci-lint-action prints the output of the linter to the console, but hidden in a "run golangci-lint" group. We want the output to be visible without having to search for that group and click on it, so we write it to a file first and then log the content of that file in a subsequent step.