Repository navigation
feat: create a branch for a work item from any branch - #38
Merged
Merged
Conversation
Branching for a work item always started from the repository's default branch, so a branch for work on a feature or hotfix line had to be made somewhere else. b now opens a full screen instead of a name prompt on the status line. It asks for the repository (preselected from the working directory), the name (prefilled as before) and the branch to create from: a fuzzy-filtered list of the repository's branches with the cursor starting on the default branch. The same screen opens from b on a work item's own pane, including one reached from a pull request. The view that opened the screen reports the outcome and copies the checkout command, so it is copied once however many views the result reaches; the work item list still syncs its row to Active either way. The status-line repository picker and RefHead are gone: each listed branch carries its commit, so no second lookup is needed. Co-Authored-By: Claude Opus 5.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
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.
Why
Branching for a work item always started from the repository's default branch, so a branch for work on a feature or hotfix line had to be made somewhere else.
What
bopens a new branch screen in place of the status-line name prompt:j/kswitches and reloads branchesrefs/headsonly), cursor on the default branchtab/shift+tabbetween fields,entercreates,escbacks outbworks on a work item's own pane too, including one reached from a pull request.azdo.Branches;RefHeadand the status-line repo picker are removed, since each listed branch carries its commit.Testing
go vet ./...andgo test ./...green.🤖 Generated with Claude Code