Skip to content

feat(ci): run clippy on codebase #764

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

Merged
merged 3 commits into from
Jun 18, 2025

Conversation

andreiltd
Copy link
Member

What is says on the tin, let's make clippy happy.

@github-advanced-security
Copy link

This pull request sets up GitHub code scanning for this repository. Once the scans have completed and the checks have passed, the analysis results for this pull request branch will appear on this overview. Once you merge this pull request, the 'Security' tab will show more code scanning analysis results (for example, for the default branch). Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. For more information about GitHub code scanning, check out the documentation.

@vados-cosmonic
Copy link
Collaborator

Thanks for adding clippy-- in the past clippy was avoided in jco because to other maintainers it seemed like not a good use of time.

That said I'm happy to have clippy be part of the linting, however can we remove the SARIF stuff and keep code scanning disabled? That's worth discussing in it's own issue before we make the change to the codebase -- I don't think it provides much benefit if we're gating on clippy to begin with.

At present this PR is titled as if it's adding clippy but it's doing much more.

@andreiltd
Copy link
Member Author

andreiltd commented Jun 18, 2025

At present this PR is titled as if it's adding clippy but it's doing much more.

Do you mean fixing the clippy issues in the code or adding SARIF?

@vados-cosmonic
Copy link
Collaborator

Adding SARIF and turning on GH Code scanning -- having clippy check and fail is certainly useful for the same reason we check the JS but the other things are a little less clear.

@andreiltd andreiltd force-pushed the clippy branch 2 times, most recently from 315b1da to c9a6e3f Compare June 18, 2025 14:29
@vados-cosmonic vados-cosmonic added this pull request to the merge queue Jun 18, 2025
Merged via the queue into bytecodealliance:main with commit d30ecf6 Jun 18, 2025
28 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants