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
Yes, I understand that the GitHub action repository is not the repository of golangci-lint itself.
Yes, I've searched similar issues on GitHub and didn't find any.
Your feature request related to a problem? Please describe.
CI result changes mid PRs / at random time because the default is "latest"
Yet I don't want to hardcode a version and get stuck in the past, I would like dependabot to tell me there is a new version of the action which would match a new version of golangci/golangci-lint
Describe the solution you'd like.
Tag/release a new action each time a new golangci/golangci-lint release is made
Add/link the release notes of golangci/golangci-lint
Describe alternatives you've considered.
Using go install/go.mod/tools but that also doesn't work because go install version of golangci/golangci-lint isn't same as binary releases (replaces...)
Additional context.
Thanks for your consideration!
The text was updated successfully, but these errors were encountered:
ldemailly
added a commit
to fortio/workflows
that referenced
this issue
Aug 23, 2024
Welcome
Your feature request related to a problem? Please describe.
CI result changes mid PRs / at random time because the default is "latest"
Yet I don't want to hardcode a version and get stuck in the past, I would like dependabot to tell me there is a new version of the action which would match a new version of golangci/golangci-lint
Describe the solution you'd like.
Tag/release a new action each time a new golangci/golangci-lint release is made
Add/link the release notes of golangci/golangci-lint
Describe alternatives you've considered.
Using go install/go.mod/tools but that also doesn't work because go install version of golangci/golangci-lint isn't same as binary releases (replaces...)
Additional context.
Thanks for your consideration!
The text was updated successfully, but these errors were encountered: