actions-marketplace-validations/Cached LFS checkout

Git checkout with LFS files from cache

View on GitHub

Trust Signals

Scorecard Score
not yet scored
Maintenance Recency
Stale
License
None
namedescriptionrequireddefault
includeExplicitly include files for LFSno*
excludeExplicitly exclude files for LFSno""
fetch-depthNumber of commits to fetch. 0 indicates all history for all tags and branchesno1
cleanWhether to execute `git clean -ffdx && git reset --hard HEAD` before fetchingnotrue
filterPartially clone against a given filter. Overrides sparse-checkout if set. ""
refThe 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. no""
repositoryRepository name with owner. For example, actions/checkout${{ github.repository }}
tokenPersonal 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) no${{ github.token }}
submodulesWhether to checkout submodules: `true` to checkout submodules or `recursive` to recursively checkout submodules. nofalse
persist-credentials'Whether to configure the token or SSH key with the local git config' notrue
enableCrossOsArchiveWhether the cache is cross-os compatible. This is useful to cache dependencies which are independent of the runner platform. This will help reduce the consumption of the cache quota and help build for multiple platforms from the same cache. [Learn more about cross-os caching](https://github.com/actions/cache/blob/main/tips-and-workarounds.md#cross-os-cache). nofalse

no outputs