malwarebytes/v1gittools

Git Flow Developer tool with VersionOne and Github Integration

v1gittools's Issues

switching/remembering stories and/or branches

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.)

changing story status should (or optionally) remember 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, 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>.

changing V1 story status commands

Running v1git develop ... or v1git qa are the only change V1 story status commands. However, the .v1git.conf file has a v1_story_statuses section for specifying (mapping) V1 story statuses (potentially others besides develop and qa).

Maybe the v1git command should also accept a command option syntax like:

v1git status <v1_story_status> [-s story_name] [-b <branch_name>]

This would be to switch the story status to <v1_story_status> and do any associated commands (e.g.: create a PR in the git repo if a PR doesn't yet exist).

Ideally, the previous story name and branch name would be assumed unless the -s or -b options were specified.

Missing Tests

This project is sorely missing tests. If we are going to grow this project, we need tests to lock down requirements and functionality.

Missing Automated Testing and Code Coverage

This project is missing TravisCI and Coveralls.

`v1git qa` errors out after 1st time

When I try v1git qa second time (possibly after bumping the story back to QA w/ v1git develop <story num>), I get:

Branch 'B-24436' does not exist on github. Did you forget to `git push`? Cannot create PR!

The error message needs clarification. Also, existence of matching PR should probably be checked.

v1git help should print version

We need to know what version v1git is at. It'd be nice if this is printed out on the help screen.

Bad URL For Defects

Defect url is:

HOSTNAME/defect.mvc/Summary?oidToken=Defect...

We have story.mvc hardcoded into the system. We should detect if it is a story or defect to link properly to the original versionone asset.

v1git should remember the story number

v1git develop <story num> bumps the story back to "In Progress" .. nice, but it would be a bit nicer if the story was optional the second time around. Likewise for other applicable commands.

v1git fails to work when inside subdirectories of a git repository

v1git fails to work when inside a subdirectory of a git repository.

{main_git_dir}/some/sub/dir/.git: path does not exist (ArgumentError)

It should work from within any directory within the repository.