Repository files (latest commit first)

Filename	Latest commit message	Latest commit date
Jason Barnett b6a00b350f Add retry logic to checkout and submoduleUpdate for partial clone resilience ... When using partial clones (filter=blob:none, which is automatically set for sparse checkouts), `git checkout` lazily fetches missing blobs from the promisor remote. If the remote is temporarily unavailable, this network call fails and surfaces as a hard error with no retry. The `fetch`, `getDefaultBranch`, and `lfsFetch` methods already use retryHelper, but `checkout` and `submoduleUpdate` did not, despite both performing network operations: - `checkout`: fetches blobs on-demand from promisor remotes during partial clone checkouts - `submoduleUpdate`: clones/fetches submodule repositories This was observed in production when GitHub's git service had a brief outage, causing the checkout step to fail with: fatal: unable to access '...': Failed to connect to github.com port 443 after 135272 ms: Couldn't connect to server fatal: could not fetch <sha> from promisor remote Wrapping both methods with the existing retryHelper (3 attempts with 10-20s jittered backoff) makes these operations resilient to transient network failures, consistent with how fetch already behaves. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>		2026-03-20 16:52:56 +00:00
..
index.js	Add retry logic to checkout and submoduleUpdate for partial clone resilience	2026-03-20 16:52:56 +00:00
problem-matcher.json	Convert checkout to a regular action (#70)	2019-12-03 10:28:59 -05:00