You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Aug 13, 2020. It is now read-only.
When typing v1git develop <story num> <branch name>, the branch name is optional. Omitting the branch name causes v1git to use a branch named according to the story number, which I assume is for auto-naming the branch to match the story number.
However, there should be a way to stay on the same branch that you are on when using 'change story status' type of commands.
For example, if you had typed v1git develop <story num> ..., made/pushed some changes, typed v1git qa, and then typed v1git develop <story num> to bump the story back to "In Progress", then you would end up creating to a new branch named <story num> and switching to it (and you might wonder which git branch is now linked to the v1 story). However, you probably intended to stay on branch <branch name>.
When typing
v1git develop <story num> <branch name>, the branch name is optional. Omitting the branch name causes v1git to use a branch named according to the story number, which I assume is for auto-naming the branch to match the story number.However, there should be a way to stay on the same branch that you are on when using 'change story status' type of commands.
For example, if you had typed
v1git develop <story num> ..., made/pushed some changes, typedv1git qa, and then typedv1git develop <story num>to bump the story back to "In Progress", then you would end up creating to a new branch named<story num>and switching to it (and you might wonder which git branch is now linked to the v1 story). However, you probably intended to stay on branch<branch name>.