Support nested branch names (e.g., feature/foo)#4
Open
sestinj wants to merge 2 commits intodadlerj:mainfrom
Open
Support nested branch names (e.g., feature/foo)#4sestinj wants to merge 2 commits intodadlerj:mainfrom
sestinj wants to merge 2 commits intodadlerj:mainfrom
Conversation
Create parent directories before writing branch refs so that branches with slashes in the name (e.g., feature/foo, nate/tin-stuff) work correctly. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
- ListBranches now uses filepath.WalkDir to find branches in subdirectories - Updated tests to use "feature/test" branch name to verify nested support Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
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.
Fixes branch operations for names containing slashes like
feature/fooornate/my-branch.Changes:
WriteBranch: Create parent directories before writing ref fileListBranches: Usefilepath.WalkDirto find branches in subdirectoriesTests updated to use
feature/testbranch name.This PR will not dilute the 100% vibe-codedness of
tin. If there are any guidelines you have in mind (e.g. maybe I should commit withtin) let me know!