jp-pino/Cache checkout and build

Checkout a repo and cache build for faster installation next time

Trust Signals

name	description	required	default
repository	Repository name with owner. For example, actions/checkout	—	${{ github.repository }}
ref	The branch, tag or SHA to checkout. When checking out the repository that triggered a workflow, this defaults to the reference or SHA for that event. Otherwise, uses the default branch.	—	""
token	Personal access token (PAT) used to fetch the repository. The PAT is configured with the local git config, which enables your scripts to run authenticated git commands. The post-job step removes the PAT. We recommend using a service account with the least permissions necessary. Also when generating a new PAT, select the least scopes necessary. [Learn more about creating and using encrypted secrets](https://help.github.com/en/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)	—	${{ github.token }}
submodules	Whether to checkout submodules: `true` to checkout submodules or `recursive` to recursively checkout submodules. Passed straight through to actions/checkout, which fetches them with the same token (SSH URLs are rewritten to HTTPS).	—	false
cmake-flags	Flags to pass to cmake on build	—	""
build-flags	Flags to pass to cmake --build on build	—	""
pre-build-command	Command to run before building	—	""
shell	The shell to use for the build steps	—	bash

name	description
cache-restore-hit	Whether the cache was hit or not on restore
cache-save-hit	Whether the cache was hit or not on save
latest-ref	The latest ref of the repository (sha)