Fix stale Rift parent and workspace name resolution - #114
Merged
Conversation
- unwrap cached managed-workspace paths to the original checkout - suffix names that already exist in the Rift registry - cover stale parent and collision resolution with regression tests
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.
Ticket
SKIPPED
Description
Prevent stale OpenCode workspace metadata from nesting new Rift workspaces beneath a removed managed parent. Normalize cached Rift paths back to the original checkout and select an available suffixed name before OpenCode registers a workspace, keeping OpenCode and Rift aligned without global registry cleanup.
Checklist
Parent Resolution
Name Resolution
Validation
bun run compilesucceedsbun run typecheckreports no errorsbun run test