ci: add staticcheck and govulncheck to CI#44
Conversation
Fixes dolph#30 Co-authored-by: Cursor <cursoragent@cursor.com>
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 9f8b144cdf
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
|
|
||
| - uses: dominikh/staticcheck-action@v1 | ||
| with: | ||
| version: latest |
There was a problem hiding this comment.
Using version: latest makes CI behavior time-dependent: each new Staticcheck release can add checks and start failing unrelated PRs even when repository code hasn’t changed. The action’s own README warns that new versions may break builds and recommends pinning a specific version, so this introduces avoidable flakiness and non-reproducible CI results.
Useful? React with 👍 / 👎.
1 participant
Fixes #30
Made with Cursor