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

chore(ci): Add clippy job to check error #1910

Merged
merged 1 commit into from
Sep 5, 2024
Merged

Conversation

tottoto
Copy link
Collaborator

@tottoto tottoto commented Sep 2, 2024

Adds clippy job to check only error to detect some kind of error like #1908 which is difficult to find.

@tottoto
Copy link
Collaborator Author

tottoto commented Sep 2, 2024

@LucioFranco Although I think you would not like running clippy on CI as you removed it #1288, I would like to ask your opinion. This time, setting it to only detect errors in order to reduce the possibility of blocking CI. I would think it is valuable because it allows us to notice important aspects.

@tottoto tottoto requested a review from LucioFranco September 2, 2024 16:42
Copy link
Contributor

@djc djc left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I like it -- in most projects we use -D warnings for clippy in CI, and have a weekly scheduled job running on Friday mornings to try and find issues from new releases quickly.

@tottoto
Copy link
Collaborator Author

tottoto commented Sep 5, 2024

Let's try applying it at this stage and see what the impact is. If it becomes an overhead for development, I think we can easily remove it again.

@tottoto tottoto added this pull request to the merge queue Sep 5, 2024
Merged via the queue into hyperium:master with commit e92b9fe Sep 5, 2024
17 checks passed
@tottoto tottoto deleted the clippy-ci branch September 5, 2024 20:42
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