Skip to content

Conversation

@kennykerr
Copy link
Collaborator

Previously, warnings were treated as errors only for PR validation. This just makes it easier to catch such issues during development and avoid unnecessary PR validation failure.

@kennykerr kennykerr merged commit 1e662ff into master Aug 19, 2024
@kennykerr kennykerr deleted the warnings-as-errors branch August 19, 2024 16:45
@MarijnS95
Copy link
Contributor

Running into this now, this seems to be hampering the developer experience. Sometimes when experimenting with bindgen code, warnings appear that disallow running tool_bindings, forcing the developer to clean up unused variables and imports before proceeding. Isn't the whole idea of a warning to allow developing code while making them aware ("warning"...) that it won't pass upstream CI (as intended) when submitted as-is?

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