mdbs99 / git-work Goto Github PK

Every time we change the git-work code, we have to do manual tests. This step consumes a lot of enfort and time. So, we need implement automated tests do improve it and garantee code quality to this project. @mdbs99 WDYT?

Let's create a new update command that will work like git pull origin <branch>, using the same approach that we used in done and push, ie, using the current branch.

I don't know whether this command could be the same for #5 or not.

It would be nice if git-work can list the opened issues, something like $ git work issues and the opened issues appear. I'll handle it.

Let's create an easy way to install git-work. For example, $ git-work.sh install. I'll handle it.

Let's add executable permission to git-work.sh. I'll handle it.

Let's polish the code. For example, change if's for case. I'll handle it.

Let's update Copyright notice to 2019.

Let's create a new command option: pr update
This command should update the current pr.
When the contributor updates his PR and it wasn't merged into master yet, we need to update the local pr to continue working.

The commands should be:

git fetch origin pull/<id>/head
git merge pull/<id>/head

The script needs to check if the current branch is a PR by prefix pr. Otherwise, the user gets an error.

We couldn't use done if we are already in master.

Let's create a new merge command.
It will be like done command, but won't change the current branch.

We can use it to merge a branch in others and continue the work until it will completely done.

Let's change the commit command a little bit to make possible to use "--amend" option.

The issue #8 has introduced a git add . command in the execution of git work commit command.
I believe this is not always good. Sometimes we need to commit just some files, not all that were changed.

@fabriciofx what will you think if we change commit command, introducing a new parameter like this?

git work commit -a "message"

This is could be related with #18 too.

Let's make a little change in commit command.
I would like to concatenate issue ID in each comment following this pattern: #id: message

We don't need to remember the issue ID for each comments.

Let's create a new config command.
This is related with #9. If the user type just git work config without any params, git-work will show all configurations.

Let's give a possibility to user could define its own main branch (default is master).
Sometimes we could not push our changes into the main branch because this could be dangerous. So, because that, the user could define its own main branch.

This parameter should be stored in .gitconfig file with an option to user choose globally or not.

This main branch will be used in done, push, and release commands.

The issue command, must have a test if the branch already exists.
Sometimes we just commit the branch (eg. 123 branch) to come back later. If we use the command git work issue 123, we will got an error because the branch already exists.

Let's abbreviate push and done subcommands doing them get the current branch name. I'll handle it.