fix: scope worktree branches to their project - #44
Merged
Merged
Conversation
- Generate temporary and readable worktree branches under a project-specific namespace - Preserve regeneration support for legacy t3code worktree branches - Update web, mobile, server tests, and source-control documentation
github-actions
Bot
added
vouch:trusted
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.
What Changed
t3code/...worktree branches for migration.Why
Worktree branches previously shared the global
t3codenamespace, which could make branches from different projects ambiguous. Project-scoped names make worktree branches easier to identify and avoid collisions while keeping older branches eligible for regeneration.UI Changes
No visual UI changes. The behavior is reflected in worktree branch names and user documentation.
Checklist