Repository navigation
fix(lastcode): describe nested vendor gitlink - #83
Merged
Merged
Conversation
Loading
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
GitHub Checkout v6 fails before the Intel artifact workflow can run because the repository contains one nested gitlink without a matching root
.gitmodulesentry.Describe that existing reference-only Alchemy dependency at the repository root, with
update = none, so checkout can inspect submodules without downloading the vendor repository. A disposable sparse checkout passes the exact recursive credential-cleanup command that failed on the Intel runner.Implemented by GPT-5.6 in the Codex harness.