You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Golang lint is a fast Go linters runner. It runs linters in parallel, uses caching, supports yaml config. It’s used to make sure code adheres to common Go practices. It supports enable many different types of linters.
I think we can introduce it to Notation to enable static code formatting scanning in each pull request.
What alternatives have you considered?
N/A
Any additional context?
No response
The text was updated successfully, but these errors were encountered:
Add golangci-lint-action to the CI workflows as it's the official GitHub action for golangci-lint from its authors. The action runs golangci-lint and reports issues from linters.
Name the new workflow as golangci-lint-action in .github/workflows/go-lint.yml
Current behaviour:
Run golangci-lint on every PR
Report only new issue generated from the PR (by using only-new-issues: true option from golangci-lint-action)
Beside of PR events, there has an option in the trigger event to allow us manually run the workflow if needed (workflow_dispatch:)
Is your feature request related to a problem?
N/A
What solution do you propose?
Golang lint is a fast Go linters runner. It runs linters in parallel, uses caching, supports yaml config. It’s used to make sure code adheres to common Go practices. It supports enable many different types of linters.
I think we can introduce it to Notation to enable static code formatting scanning in each pull request.
What alternatives have you considered?
N/A
Any additional context?
No response
The text was updated successfully, but these errors were encountered: