-
Notifications
You must be signed in to change notification settings - Fork 1
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
ci: Add cargo #6
Conversation
`taplo lint` and `taplo format`, in that order, have been add on push and pull request into any branch.
Add a configuration file for taplo so CI and local can use the same taplo rules.
Switch from Action for taplo CI to manual install and running. Use only `taplo format` and remove `taplo lint` check.
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.
LGTM but it seems to have changes from the taplo PR, is that correct?
Yes, I branched off of the taplo branch. I'll fix the conflicts |
The merge-base changed after approval.
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.
LGTM
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.
Great! Thank you! 🔥
Add cargo CI jobs as described in #3. At the moment we have a single cargo job that runs
clippy
,build
andtest
.Some notes about build times on my local env:
cargo build --release
: 27m48scargo build -p polka-storage-node --features runtime-benchmarks
: 20m21scargo build -p polka-storage-runtime
: 5m50scargo build --features try-runtime
: 19m25s