Repository navigation
Conversation
Git's worktree records allow every command to find checkouts outside the default layout. Keep branch identity separate from the public worktree name so directory-derived names do not change Git operations. Preserve names for existing standard-layout checkouts and reserve explicit names recorded in each checkout's Git directory. Manual checkouts use progressively longer path suffixes to resolve conflicts within a repository.
Custom checkout parents belong to the user, not Timber's layout, so removal must leave them intact. Prune retains selected worktree identities because removing a conflicting checkout can change the directory-derived names of the remaining checkouts. Force removal must also work for manual branches without an upstream; only non-force removal needs cleanliness and merge checks. Verify that repository renames retain custom paths and keep them addressable.
Users can place a checkout where their workflow needs it without losing Timber's lifecycle commands or shell integration. Resolve relative destinations against the invocation directory and record the explicit or generated name in worktree-scoped Git metadata. Reserve visible names before creating another checkout and include custom checkouts when choosing generated names. Complete the second argument as a directory while retaining existing name completion for the first argument.
Custom-location and manual worktrees cannot be located from their names alone. Let users show checkout paths without widening the default listing. The location column stays last when PR status is also requested; JSON output already includes the path.
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.
No description provided.