fix: make sync-link repo selection deterministic for e2e#55
Merged
iHildy merged 4 commits intoian/add-turso-session-backendfrom Apr 13, 2026
Merged
Conversation
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Code Review
This pull request introduces a "strict link" mode and the ability to disable repository auto-discovery, primarily for E2E testing. It adds environment variable support to enforce specific repository targets and implements a parseRepoReference utility to handle GitHub repository identifiers in HTTP, SSH, and short-name formats. Review feedback suggests enhancing the robustness of the parsing logic by supporting ssh:// protocols, allowing optional trailing slashes in SSH strings, and adding validation to the generic owner/repo parser to prevent false positives from malformed input.
🤖 Review Jules RelayI found 1 Gemini suggestion so far. Type |
iHildy
added a commit
that referenced
this pull request
Apr 13, 2026
* feat: add Turso session backend with setup and migration commands * fix: make sync-link repo selection deterministic for e2e (#55) * fix: make sync-link repo selection deterministic for e2e * fix: harden turso runtime session sync safety * fix: harden repo reference parsing for PR feedback * refactor: reduce turso sync io overhead * fix: harden turso session sync transport and timeouts
iHildy
added a commit
that referenced
this pull request
Apr 13, 2026
* fix: expand e2e coverage and docs for session sync compatibility * feat: add Turso session backend for concurrent-safe sync (#54) * feat: add Turso session backend with setup and migration commands * fix: make sync-link repo selection deterministic for e2e (#55) * fix: make sync-link repo selection deterministic for e2e * fix: harden turso runtime session sync safety * fix: harden repo reference parsing for PR feedback * refactor: reduce turso sync io overhead * fix: harden turso session sync transport and timeouts * fix: avoid mutating string values when parsing JSONC
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
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.
Summary
Validation