You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Rust community expressed the need to create a CI check to ensure that no manual modifications have been made to the vendored generated code produced by Weaver. See this comment.
One option would be to update Weaver to generate a checksum (e.g., SHA256) for the generated code and store it in a file alongside the generated code. This would provide everything needed to create a CI check to verify that no manual changes have been made to the code in the repository, assuming we’ve also prevented rust fmt (or any other code formatter) from altering the generated code.
The text was updated successfully, but these errors were encountered:
The Rust community expressed the need to create a CI check to ensure that no manual modifications have been made to the vendored generated code produced by Weaver. See this comment.
One option would be to update Weaver to generate a checksum (e.g., SHA256) for the generated code and store it in a file alongside the generated code. This would provide everything needed to create a CI check to verify that no manual changes have been made to the code in the repository, assuming we’ve also prevented
rust fmt
(or any other code formatter) from altering the generated code.The text was updated successfully, but these errors were encountered: