f3d-app/Cache LFS data
Recover LFS data using cache when possible
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Activelast commit Jun 28, 2026
- License
- BSD
Pinned Snippet
uses: f3d-app/lfs-data-cache-action@f462a7763a17f8614f8fd81ba8e4ef18f74d37de # v2.2tags can be moved; commit SHAs can't. why a SHA?
Inputs
| name | description | required | default |
|---|---|---|---|
| type | Whether this action produce/consume LFS data | — | producer |
| repository | Repository to recover LFS data from | no | ${{ github.repository }} |
| ref | branch, tag or SHA to checkout and look for LFS data in | no | "" |
| lfs_sha | LFS sha to recover. If not set, target directory will be used to recover it. | no | — |
| cache_postfix | A postfix to differentiate between caches | — | cache |
| target_directory | Existing directory to copy LFS data to | — | source |
Outputs
| name | description |
|---|---|
| lfs_sha | The lfs_sha generated by a producer action |