Skip to content

Use warm full-history caches without starting another task - #3

Merged
PandelisZ merged 1 commit into
masterfrom
pz/checkout-full-history-warm
Oct 18, 2026
Merged

PandelisZ merged 1 commit into
masterfrom
pz/checkout-full-history-warm

Conversation

@PandelisZ

@PandelisZ PandelisZ commented Oct 18, 2026 •

Copy link
Copy Markdown
Contributor

Full-history checkouts were waiting for a preparation task even when every branch and tag was already cached. On TextYess, task startup plus polling could exceed the ten-second wait and trigger a GitHub fetch despite a warm cache.

For a trusted cached commit, read the current branch/tag advertisement using checkout's configured Git credentials. When every advertised tip has a completion marker on the read-only mount, create local refs and use those objects immediately. New tips still go through the existing authenticated preparation path. Tag-targeted checkouts keep that path as well.

Validation: 139 action tests pass, including a real Git full-history/tag checkout with no preparation API request, newly advertised tips requiring preparation, malformed ref rejection, and upstream credential cleanup. Lint, formatting and rebuilt distribution pass. Release 1.0.2 under the existing 1 major tag.

Hosted proof: TextYess full-history checkout uses the released major tag at e462767, reports warm Git object cache, performs no GitHub object fetch, and completes checkout in about two seconds. The preceding rerun took 18 seconds and fell back. Released as 1.0.2 and the existing major tag 1.

@PandelisZ
PandelisZ merged commit e462767 into master Oct 18, 2026
2 checks passed
@PandelisZ
PandelisZ deleted the pz/checkout-full-history-warm branch October 18, 2026 04:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant