v2 upgrade: is there a suitable alternative to --out-format=github-actions
?
#5703
-
Congrats on the massive milestone of v2 and the great work being done 🚀 I'm just getting around to picking up some of the upgrades, and notice that i.e. on oapi-codegen/oapi-codegen#1940 I see:
Looking at https://golangci-lint.run/product/migration-guide/#command-line-flags I don't see an option for GitHub Actions - is it that this was deprecated without a replacement, or maybe that it doesn't need a specific output to be picked up accordingly? Or maybe that using a |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
Hello, Thank you. The The GitHub action can parse the default golangci-lint output format ( https://github.com/golangci/golangci-lint-action/tree/main?tab=readme-ov-file#problem-matchers About the "unknown flag: --out-format": |
Beta Was this translation helpful? Give feedback.
Hello,
Thank you.
The
github-actions
format is deprecated since v1.59 (2024-05-26).And this format is not supported by the GitHub action since v6.0.0 (2024-05-07)
The GitHub action can parse the default golangci-lint output format (
--output.text.path=stdout
).https://github.com/golangci/golangci-lint-action/tree/main?tab=readme-ov-file#problem-matchers
About the "unknown flag: --out-format":