It is console tool which allows to create release and pre-release tags and branches in different git engines:
- github (beta)
- bitbucket (beta)
- bitlab (beta)
- local (rleased)
- remote (beta)
The workflow looks as follows:
- Init configuration. It can be the folder of the project or any other folder. The tool does not depend on the repository. It requires api token for gitlab/bitbucket/gitlab.
- Start feature. It creates the branch with prefix
feature/
. - Test feature. It marks feature as
release candidate
and is used to compileRelease Candidate
- Release feature. It marks feature as
release stable
and is used to compileRelease Stable
. - Create Release Candidate. It creates
Release Candidate
branch and tag. - Create Release Stable. It creates
Release Stable
branch and tag.
Go to latest release and download git-release-man.phar
https://github.com/vdubyna/git-release-man/releases/latest
./git-release-man.phar g:b init
./git-release-man.phar g:f start --name FEATURE_NAME_HERE
Removes feature branch from repository
./git-release-man.phar g:f close --name FEATURE_NAME_HERE
Removes labels from feature. It exclude feature from builds.
./git-release-man.phar g:f reset --name FEATURE_NAME_HERE
./git-release-man.phar g:b features-list
./git-release-man.phar g:f release-candidate --name FEATURE_NAME_HERE
./git-release-man.phar g:f release-stable --name FEATURE_NAME_HERE
./git-release-man.phar g:b release-candidate
./git-release-man.phar g:b release-stable
./git-release-man.phar g:b latest-release-candidate
./git-release-man.phar g:b latest-release-stable
# generate secure token for travis, is required to deploy release
travis encrypt api_key_here
# Add api key variable to env
travis env set GITHUBKEY api_key_here --private -r vdubyna/git-release-man