Skip to content
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

Merged
merged 4 commits into from
Oct 1, 2024
Merged

[TST] Move clippy into the lint job #2886

merged 4 commits into from
Oct 1, 2024

Conversation

HammadB
Copy link
Collaborator

@HammadB HammadB commented Oct 1, 2024

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?

  • Tests pass locally with pytest for python, yarn test for js, cargo test for rust

Documentation Changes

None

Copy link

github-actions bot commented Oct 1, 2024

Reviewer Checklist

Please leverage this checklist to ensure your code review is thorough before approving

Testing, Bugs, Errors, Logs, Documentation

  • Can you think of any use case in which the code does not behave as intended? Have they been tested?
  • Can you think of any inputs or external events that could break the code? Is user input validated and safe? Have they been tested?
  • If appropriate, are there adequate property based tests?
  • If appropriate, are there adequate unit tests?
  • Should any logging, debugging, tracing information be added or removed?
  • Are error messages user-friendly?
  • Have all documentation changes needed been made?
  • Have all non-obvious changes been commented?

System Compatibility

  • Are there any potential impacts on other parts of the system or backward compatibility?
  • Does this change intersect with any items on our roadmap, and if so, is there a plan for fitting them together?

Quality

  • Is this code of a unexpectedly high quality (Readability, Modularity, Intuitiveness)

@HammadB HammadB changed the title [TST] Move clippy into its own job [TST] Move clippy into the lint job Oct 1, 2024
- name: Cargo fmt check
shell: bash
run: cargo fmt -- --check
- name: Clippy
run: cargo clippy --all-targets --all-features --keep-going -- -D warnings
Copy link
Contributor

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?

Copy link
Collaborator Author

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.

@HammadB HammadB merged commit 9a46096 into main Oct 1, 2024
68 of 70 checks passed
itaismith pushed a commit that referenced this pull request Oct 10, 2024
## 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
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.

3 participants