checkout/.github/workflows
Andrew Klotz 604bd602e9 Materialize LFS objects with an explicit git lfs checkout
Problem

On persistent/self-hosted runners that reuse a working directory across jobs, LFS-tracked files can be left as pointer files instead of real content when a lfs: false checkout precedes a lfs: true checkout of the same repo.

Sequence that triggers it:
 1. A lfs: false run sets GIT_LFS_SKIP_SMUDGE=1, so git checkout writes LFS files to the working tree as pointers.
 2. A later lfs: true run on the same worktree fetches the objects into .git/lfs, but git checkout sees the tree already at the target commit and does not re-smudge the already-present pointer files.

Result: the objects are in the local cache, but the working tree still contains pointers. The action relies on the smudge filter firing during git checkout to materialize content — which holds on a clean tree (GitHub-hosted runners) but not on a reused one.

Related: actions/checkout#270
2026-08-06 22:49:29 +00:00
..
check-dist.yml Update all references from v5 and v4 to v6 (#2314) 2025-11-23 19:32:55 -06:00
codeql-analysis.yml Update all references from v5 and v4 to v6 (#2314) 2025-11-23 19:32:55 -06:00
licensed.yml Update all references from v5 and v4 to v6 (#2314) 2025-11-23 19:32:55 -06:00
publish-immutable-actions.yml Update all references from v5 and v4 to v6 (#2314) 2025-11-23 19:32:55 -06:00
test.yml Materialize LFS objects with an explicit git lfs checkout 2026-08-06 22:49:29 +00:00
update-main-version.yml Update all references from v5 and v4 to v6 (#2314) 2025-11-23 19:32:55 -06:00
update-test-ubuntu-git.yml Update all references from v5 and v4 to v6 (#2314) 2025-11-23 19:32:55 -06:00