Cross-platform composite GitHub Action for Rust Workflows

Check the .github/workflows directory for usage examples.

Below are the steps that this GitHub action undertakes:

Checks out the target git repository in the runner container. Uses actions/checkout

Selects the Rust toolchain components to install based on the provided subcommand. If one of the supported subcommands (see examples above) is not provided, the following components are installed.

Installs the Rust toolchain based on the provided information about the release channel, the compilation target, and the toolchain components. Uses dtolnay/rust-toolchain.

Installs cross-rs. Uses taiki-e/install-action.

Installs cargo-llvm-cov(https://github.com/taiki-e/cargo-llvm-cov) if necessary. Uses taiki-e/install-action.

Sets up Rust cache. Uses Swatinem/rust-cache

Runs the given subcommand using cargo and the provided arguments, if the input use_cross is not true.

Runs the given subcommand using cross and the provided arguments, if the input use_cross is true.

Collects all possible outputs in a common directory (target/.dist). This is necessary because Cargo creates numerous files and directories at different levels of nesting with no fixed path to the binaries or the documentation across all platforms.

Uploads the files in the form of an artifact and names it artifact-${{ inputs.subcommand }}-${{ inputs.compilation_target }}. Some examples of possible artifact names: artifact-build-x86_64-unknown-linux-gnu, artifact-doc-x86_64-unknown-linux-gnu, artifact-build-x86_64-pc-windows-msvc, artifact-build-aarch64-apple-darwin.

The artifact that contains the built binaries or documentation if relevant. Otherwise none. The action fails if any of the steps encounter an error. Otherwise it succeeds.