-
Notifications
You must be signed in to change notification settings - Fork 22
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
Cargo workflow #21
Cargo workflow #21
Conversation
Finally fixed the issue. Somehow, for new nightly releases, cargo fmt output is not consistent. 🤦 Tried a lot of different things, cost me some hours... |
Will squash-merge, commit history is not important for this PR |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
for cargo check: clippy itself runs cargo check: https://github.com/rust-lang/rust-clippy/blob/c154754b74577906c5d55d57f7daeff02d6a33e7/src/main.rs#L59
Didn't know this, thanks for sharing!
This PR is providing a template for running the most important cargo commands in our CI-test.
We can use this CI as a condition in our PRs, so even if we forget to run cargo clippy for example, github won't :)
I've configured it, so that it will only run the test in ubuntu machines, but not on windows and macos. I thought running on all 3 major OS for each run would be an overkill.
If we want to run the test on macos and windows, I've added a dispatch option, we can manually dispatch this test on macos and windows.