Conversation
Two bugs prevented proper worktree management: 1. `ez create --from` never created a worktree because the condition `!no_worktree && from.is_none()` treated --from as implying no-worktree. The --from flag controls which branch is the parent, not whether a worktree is created. Now `ez create feat --from main` creates a worktree at .worktrees/feat as expected. 2. `ez switch` fell back to `git checkout` for branches without worktrees, hijacking the main worktree. Now it auto-creates a linked worktree for managed branches that don't have one, matching the worktree-first design.
…no-switch, duplicate branch, and switch_to edge cases
…ag, missing middle)
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.
Part of a stack managed by
ez.Stack (this PR is 1 of 1):