-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
[TST] Move clippy into the lint job #2886
Conversation
Reviewer ChecklistPlease leverage this checklist to ensure your code review is thorough before approving Testing, Bugs, Errors, Logs, Documentation
System Compatibility
Quality
|
- name: Cargo fmt check | ||
shell: bash | ||
run: cargo fmt -- --check | ||
- name: Clippy | ||
run: cargo clippy --all-targets --all-features --keep-going -- -D warnings |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
maybe we should modify the steps in this workflow to always run, even if one errors?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good point. Updated so that it continues-on-error for non-setup steps so that if setup fails, the job fails.
## Description of changes *Summarize the changes made by this PR.* - Improvements & Bug fixes - Moves clippy into its own job so that we don't block tests. It is good to be able to run these separately. - Unifies the rust lint jobs into the lint action, where `cargo fmt` was already running. - New functionality - None ## Test plan *How are these changes tested?* - [x] Tests pass locally with `pytest` for python, `yarn test` for js, `cargo test` for rust ## Documentation Changes None
Description of changes
Summarize the changes made by this PR.
cargo fmt
was already running.Test plan
How are these changes tested?
pytest
for python,yarn test
for js,cargo test
for rustDocumentation Changes
None