actions-marketplace-validations/Cached LFS checkout
Git checkout with LFS files from cache
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Stale
- License
- None
Inputs
| name | description | required | default |
|---|---|---|---|
| include | Explicitly include files for LFS | no | * |
| exclude | Explicitly exclude files for LFS | no | "" |
| fetch-depth | Number of commits to fetch. 0 indicates all history for all tags and branches | no | 1 |
| 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. | no | "" |
| repository | Repository name with owner. For example, actions/checkout | — | ${{ github.repository }} |
| 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) | no | ${{ github.token }} |
| submodules | Whether to checkout submodules: `true` to checkout submodules or `recursive` to recursively checkout submodules. | no | false |
Outputs
no outputs