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.

Sign up for GitHub

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

Jump to bottom

Update workflow to fix Clippy checks #330

Merged
merged 4 commits into from
Jul 10, 2023
Merged

Update workflow to fix Clippy checks #330

merged 4 commits into from
Jul 10, 2023

Conversation

Rigidity
Copy link
Contributor

No description provided.

@Rigidity Rigidity marked this pull request as draft July 10, 2023 00:38
@coveralls-official
Copy link

coveralls-official bot commented Jul 10, 2023 •
edited

Pull Request Test Coverage Report for Build 5502967861

  • 35 of 35 (100.0%) changed or added relevant lines in 5 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage increased (+0.02%) to 93.893%
Totals Coverage Status
Change from base Build 5502321570: 0.02%
Covered Lines: 5212
Relevant Lines: 5551
💛 - Coveralls

@Rigidity Rigidity marked this pull request as ready for review July 10, 2023 01:16
@Rigidity Rigidity requested a review from arvidn July 10, 2023 02:01
@Rigidity Rigidity merged commit c4a8c8e into main Jul 10, 2023
21 checks passed
@arvidn arvidn deleted the update-workflow branch July 10, 2023 17:53
MarvinQuevedo pushed a commit to MarvinQuevedo/clvm_rs that referenced this pull request Aug 26, 2023
@Rigidity @MarvinQuevedo
Update workflow to fix Clippy checks (Chia-Network#330)
113fbef 
* Replace clippy-check with cargo clippy

* Add --all-targets and --workspace

* Fix clippy warnings

* Fix formatting
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@arvidn arvidn arvidn approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
2 participants
@Rigidity @arvidn