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

make lint / make gosec failed if golangci-lint / gosec is not installed #1127

Closed
yosmoc opened this issue Oct 13, 2021 · 0 comments · Fixed by #1128
Closed

make lint / make gosec failed if golangci-lint / gosec is not installed #1127

yosmoc opened this issue Oct 13, 2021 · 0 comments · Fixed by #1128
Labels
🐛 bug "Houston, we've had a problem."

Comments

@yosmoc
Copy link
Contributor

yosmoc commented Oct 13, 2021

What's broken?

$ make lint
golangci-lint cache clean
make: golangci-lint: No such file or directory
make: *** [Makefile:105: lint] Error 127
yosmoc added a commit to yosmoc/wtf that referenced this issue Oct 13, 2021
fix wtfutil#1127

Install golangci-lint / gosec, if it is not installed.
If we only support over go 1.16, we should use go install instead of go
get.

Use binary installation for golangci-lint because they recommends.
https://golangci-lint.run/usage/install/#local-installation
@senorprogrammer senorprogrammer added the 🐛 bug "Houston, we've had a problem." label Oct 14, 2021
yosmoc added a commit to yosmoc/wtf that referenced this issue Oct 14, 2021
fix wtfutil#1127

Install golangci-lint / gosec, if it is not installed.
Use binary installation for golangci-lint because they recommend.
https://golangci-lint.run/usage/install/#local-installation
senorprogrammer pushed a commit that referenced this issue Oct 17, 2021
fix #1127

Install golangci-lint / gosec, if it is not installed.
Use binary installation for golangci-lint because they recommend.
https://golangci-lint.run/usage/install/#local-installation
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🐛 bug "Houston, we've had a problem."
Development

Successfully merging a pull request may close this issue.

2 participants