fix: support nested repositories in workspace checkpoints - #1902
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.
Pull Request
Related Issue
Closes #1901
Description
This fixes workspace checkpoint failures after a task clones an independent Git repository inside a Git-managed Space.
Git reports an untracked nested repository as a single directory entry such as
?? child-repository/. The checkpoint path pipeline normalized the correspondingPathtochild-repository, causingpath_sourcesvalidation to fail after the clone had already completed. The tool outcome was then marked unknown and the Run failed.The parent Content Repository now treats a verified untracked nested Git root as an independent repository boundary. It excludes that boundary from parent checkpoint/status ownership without modifying ignore files or staging an implicit gitlink. Physical worktree cleanliness remains unchanged so isolated worktrees are not cleaned while they contain an unmerged nested repository.
A regression test covers creating a child repository during a broad terminal mutation and verifies that:
Testing Evidence (REQUIRED)
Locally verified command output:
What is the purpose of this pull request?
Contribution Guidelines Acknowledgement