Repository navigation
Publish Composal Checkout with persistent Git object reuse - #1
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Publish
composalai/checkout@1with a read-only persistent Git object cache on Composal runners. Warm exact-commit checkouts reuse mounted objects without a network fetch; cold or unsupported cases use the standard GitHub transport. Working trees and Git metadata remain local, with an optional dissociation step for later container actions.Based on the MIT-licensed actions/checkout v7 source pinned in UPSTREAM.md. Standard inputs, authentication, fork guards and post-job credential cleanup are retained. The compiled distribution is committed.
Validation: 136 tests pass, including real Git shallow/full-history/tag/sparse checkout, empty mount bootstrap, asynchronous ticket polling, fallback and dissociation. Lint and build pass; production dependency audit reports no vulnerabilities. CI also exercises this action on GitHub-hosted runners without a Composal mount. Hosted cache performance is verified separately after the platform rollout.