-
Notifications
You must be signed in to change notification settings - Fork 350
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
Investigate cargo make #171
Comments
Let's analyse this along with #172 We can either use it or close the issue as "won't fix" with a reason (not very helpful). But let's handle it somehow. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I came across
cargo make
when looking for code coverage CI tools.Looking at it's readme, it seems like it can run locally or in CI, and has a whole of of power to script steps (which we do now in circle.yaml). As well as having some useful standard setups.
Please try out
cargo make
for automating the various tasks we do in the CI (so we can run them locally just as easily). This includes building native, building wasm, running unit tests, checking fmt and clippy errors. It would also be good to investigate enabling some code coverage metrics.The text was updated successfully, but these errors were encountered: