Setting up unified CI for rust repos

[galargh]

Similarly to #235, it would be great to have a common way of setting up CI for rust repos too.

I'm creating this issue now to make sure we take into account rust-specific needs when we work on making the unified CI framework more customisable(to support JS workflows initially).

@laudiacay @mxinden Do you have any ideas/examples of what kind of workflows we might want to consider common in the rust world?

[mxinden]

Thanks @galargh for tracking this!

For the reference, rust-libp2p's workflow which served us well thus far.

A couple of tools which I think should be standard across repositories:

• rust-fmt
• cargo clippy
• cargo doc with intra-doc check
• cargo build (including benchmarks)
• cargo test (including benchmarks)
• build and test on WASM (if repo targets WASM)

[laudiacay]

Seconded on this! Figuring out workspaces and features being handled correctly is also important but may vary by repo.

…

On Mon, Dec 13, 2021 at 11:42 AM Max Inden ***@***.***> wrote: Thanks @galargh <https://github.com/galargh> tracking this! For the reference, rust-libp2p's workflow <https://github.com/libp2p/rust-libp2p/blob/master/.github/workflows/ci.yml> which served us well thus far. A couple of tools which I think should be standard across repositories: - rust-fmt - cargo clippy - cargo doc with intra-doc check - cargo build (including benchmarks) - cargo test (including benchmarks) - build and test on WASM (if repo targets WASM) — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#251 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACDPMJG63BPAIGFZOS264STUQYV7BANCNFSM5J5W5H7A> .

[galargh]

This issue was transferred to ipdxco/unified-github-workflows#38 in preparation for archiving of this repository.