$cd ~
$curl https://raw.github.com/nvie/gitflow/develop/contrib/gitflow-installer.sh > gitflow-installer.sh
$git clone https://github.com/nvie/gitflow.git
$rmdir gitflow/shFlags
$git clone https://github.com/nvie/shFlags.git
$mv shFlags/ gitflow/
$vim gitflow-installer.sh
# Does this need to be smarter for each host OS?
if [ -z "$INSTALL_PREFIX" ] ; then
INSTALL_PREFIX="/usr/local/bin"
fi
=> INSTALL_PREFIX="/home/zuqqhi2/.gitflow"
$ bash gitflow-installer.sh
### gitflow no-make installer ###
Installing git-flow to /home/zuqqhi2/.gitflow
Using existing repo: gitflow
Submodules look up to date
`gitflow/git-flow' -> `/home/zuqqhi2/.gitflow/git-flow'
`gitflow/git-flow-init' -> `/home/zuqqhi2/.gitflow/git-flow-init'
`gitflow/git-flow-feature' -> `/home/zuqqhi2/.gitflow/git-flow-feature'
`gitflow/git-flow-hotfix' -> `/home/zuqqhi2/.gitflow/git-flow-hotfix'
`gitflow/git-flow-release' -> `/home/zuqqhi2/.gitflow/git-flow-release'
`gitflow/git-flow-support' -> `/home/zuqqhi2/.gitflow/git-flow-support'
`gitflow/git-flow-version' -> `/home/zuqqhi2/.gitflow/git-flow-version'
`gitflow/gitflow-common' -> `/home/zuqqhi2/.gitflow/gitflow-common'
`gitflow/gitflow-shFlags' -> `/home/zuqqhi2/.gitflow/gitflow-shFlags'
$vim .bashrc
export PATH=$PATH:$HOME/.gitflow
$git flow init
Which branch should be used for bringing forth production releases?
- master
Branch name for production releases: [master]
Branch name for "next release" development: [develop]
How to name your supporting branch prefixes?
Feature branches? [feature/]
Release branches? [release/]
Hotfix branches? [hotfix/]
Support branches? [support/]
Version tag prefix? []
$git branch
* develop
master
git-flowの参考URL
http://qiita.com/items/b4d9331ec3952dbe5205
git-flowのインストール
It seems to work with following commands.
$cd ~
$curl https://raw.github.com/nvie/gitflow/develop/contrib/gitflow-installer.sh > gitflow-installer.sh
$git clone https://github.com/nvie/gitflow.git
$rmdir gitflow/shFlags
$git clone https://github.com/nvie/shFlags.git
$mv shFlags/ gitflow/
$vim gitflow-installer.sh
# Does this need to be smarter for each host OS?
if [ -z "$INSTALL_PREFIX" ] ; then
INSTALL_PREFIX="/usr/local/bin"
fi
=> INSTALL_PREFIX="/home/zuqqhi2/.gitflow"
$ bash gitflow-installer.sh
### gitflow no-make installer ###
Installing git-flow to /home/zuqqhi2/.gitflow
Using existing repo: gitflow
Submodules look up to date
`gitflow/git-flow' -> `/home/zuqqhi2/.gitflow/git-flow'
`gitflow/git-flow-init' -> `/home/zuqqhi2/.gitflow/git-flow-init'
`gitflow/git-flow-feature' -> `/home/zuqqhi2/.gitflow/git-flow-feature'
`gitflow/git-flow-hotfix' -> `/home/zuqqhi2/.gitflow/git-flow-hotfix'
`gitflow/git-flow-release' -> `/home/zuqqhi2/.gitflow/git-flow-release'
`gitflow/git-flow-support' -> `/home/zuqqhi2/.gitflow/git-flow-support'
`gitflow/git-flow-version' -> `/home/zuqqhi2/.gitflow/git-flow-version'
`gitflow/gitflow-common' -> `/home/zuqqhi2/.gitflow/gitflow-common'
`gitflow/gitflow-shFlags' -> `/home/zuqqhi2/.gitflow/gitflow-shFlags'
$vim .bashrc
export PATH=$PATH:$HOME/.gitflow
$git flow init
Which branch should be used for bringing forth production releases?
- master
Branch name for production releases: [master]
Branch name for "next release" development: [develop]
How to name your supporting branch prefixes?
Feature branches? [feature/]
Release branches? [release/]
Hotfix branches? [hotfix/]
Support branches? [support/]
Version tag prefix? []
$git branch
* develop
master
