Currently, to 'switch' to a new story and/or branch, you type:
v1git develop v1_story_id [branch_name]
This 'switches' the user to a v1 story and a git branch, putting that story into "In Develop" status.
Depending on your teams V! setup or other reasons, you might want to 'start' a story in a different status (see #4 ) or possibly create multiple branches per story (e.g.: try multiple code approaches).
So, maybe, to switch to a different story and/or branch, the v1git command should also accept a command option syntax like one of the following:
v1git switch [-s story_name] [-b branch_name]
v1git switch [-sb story_same_as_branch_name]
v1git [-s story_name] [-b branch_name]
v1git [-sb story_same_as_branch_name]
... and the story and branch name would be remembered (as applicable) for future v1git commands.
And, then to change the story status (and associated git repo commands), you'd do something like noted in #4
v1git status <v1_story_status> [-s story_name] [-b <branch_name>]
(Maybe use some other key words/options instead of 'switch' or 'status' or '-s' to keep them less similar.)
Currently, to 'switch' to a new story and/or branch, you type:
This 'switches' the user to a v1 story and a git branch, putting that story into "In Develop" status.
Depending on your teams V! setup or other reasons, you might want to 'start' a story in a different status (see #4 ) or possibly create multiple branches per story (e.g.: try multiple code approaches).
So, maybe, to switch to a different story and/or branch, the v1git command should also accept a command option syntax like one of the following:
... and the story and branch name would be remembered (as applicable) for future v1git commands.
And, then to change the story status (and associated git repo commands), you'd do something like noted in #4
(Maybe use some other key words/options instead of 'switch' or 'status' or '-s' to keep them less similar.)