repejota / git-hub Goto Github PK

Description

And show log messages if verbose is true

Description

And open the new issue url to the specified repository

• Deprecrate and remove --version flag on git hub command.

git hub issue start will:

• Assign myself to the issue
• Create a local branch with name format "issues/ID-titleslug"
• Publish this local branch to origin

Description

Currently shows:

2018/06/05 01:33:40 GET https://api.github.com/repos/repejota/test/issues/101: 404 Not Found []

Description

on start issue command check the issue status, if it is already closed/merged you should not start working on it.

Description

move coverage reports to codecov

Refactor 'git hub issue list' like 'git hub info'

Description

Add support for 'git hub release finish' that finishes an already started release.

Steps to reproduce

1. go to master branch
2. git pull --rebase --prune origin
3. git merge --no-ff --no-edit release/version_number
4. git push
5. git tag -a version_number -m "version_number"
6. git push origin --tags
7. delete remote branch "release/version_number"
8. delete local branch "release/version_number"

git hub issue command will:

Show usage for start, finish, list subcommands and exit

Description

refactor code

Implement 'feature' command.

It should execute "release start" and "release finish" commands bumping only patch version.

• decouple execution of the command

Description

Implement "git hub info" command.

This command, shows information about the local repository and remote github project.

A simple minor release command will:

git hub release start

• Be sure we are on the master branch.
• Pull latest changes.
• Calculate the new minor version.
• Create a local branch release/x.y.z (new version number).
• Push this local branch to origin.
• Modify or create VERSION file.
• Commit changes with message "Bump version".

Description

It will open the default browser to create a new issue.

Create basic documentation about the flow used by this tool.

• Purpose
• Feature branches
• Release branches
• Etc ...

Show output on 'release start' and 'release end' commands

git hub release command will:

• Show usage for start, finish, list subcommands and exit

Description

show only the semver version number

Description

`git hub issue list --project org/repo'

will show the issues of the project specified by the flag instead the current repo.

git hub issue list should:

• List available issues from the github project

Implement git hub version command that shows application version information to stdout.

To allow integration with github calls to the API need to be authenticated.

By default the github token will be readed from GITHUB_TOKEN environment variable but a global flag must be added.

Description

Name of the local branch will be "issue/org-repo-id-slug"

Implement 'feature start' command