feat: allow setting custom target branch name when creating tasks #132
Conversation
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.
Adds the ability to specify a custom branch name when creating a new task, providing more control over git branch naming conventions. This change also clarifies the branch selection options by renaming the existing
--branchflag to--source-branch.Closes #128
Changes
--target-branchoption to specify a custom name for the worktree branch instead of auto-generated names--branchoption to--source-branchfor clarity about its purpose as the base branchNotes
The auto-generated branch naming pattern (
rover/task-{id}-{randomString}) is still used by default when no custom target branch is specified. This maintains backward compatibility while giving users the flexibility to use their own branch naming conventions when needed.