Easy 4 steps to get it done Oh! Original document Address: Https://github.com/nvie/gitflow/wiki/Windows. =================================================================== Pre-condition: The computer has git installed (the installation package is attached)
STEP1:Download and install
getopt.exe
From the Util-linux to
C:\Program Files\Git\bin
. (Only
getopt.exe
, the others util-linux files is not used). Also Install
libintl3.dll
and
libiconv2.dll
From the Dependencies packages (Libintl and Libiconv), into the same directory.Description:DownloadUtil-linux-ng-2.14.1-bin package (visible attachment), put the package in the Util-linux-ng-2.14.1-bin\bin directory Getopt.exe,
libintl3.dll
And
libiconv2.dll,这3个文件放到你git的安装目录中的bin目录下。
Step2:
Clone the Git-flow sources from GitHub:
$ git clone --recursive git://github.com/nvie/gitflow.git$ cd gitflow
说明:
Then execute the above command, download the source code, and CD to the Gitflow directory.
STEP3:
Run the msysgit-install
script from a command-line prompt (your may has to run it with ' full Administrator ' rights if you installed Msysgit with it installer, and ensure you ' re running from a Windows command prompt, not MINGW):
C:\gitflow> contrib\msysgit-install.cmd
Description
Then use the CMD command, CD to just download down the gitfow contrib directory, execute msysgit-install.cmd command, note to administrator permissions, (error regret prompted, followed by git installation path name)
STEP4:
In Git bash create a symbolic link for git-flow so, can actually use the command from any location $ git flow
.
$ ln -s /C/gitflow/git-flow git-flow
说明:
Replace the/c/gitflow/path above with the actual path of the downloaded Gitflow
Now that you've finished the installation, you can try the git flow command, which is the normal init message.
(Git uses the document: http://danielkummer.github.io/git-flow-cheatsheet/index.zh_CN.html)
$ git flow init
Which branch should is used for bringing forth production releases?
-3.24banner
-Dayloan
-Dev
-fix1.5.0
-Fix1.5.0_5
-fix_issue_74
-Master
-release1.2
Branch name for production releases: [Master]
Which branch should is used for integration of the "next release"?
-3.24banner
-Dayloan
-Dev
-fix1.5.0
-Fix1.5.0_5
-fix_issue_74
-release1.2
Branch name for "Next release" Development: [Master] Dev
How to name your supporting branch prefixes?
Feature branches? [Feature/]
Release branches? [release/]
Hotfix branches? [hotfix/]
Support branches? [support/]
Version tag prefix? []
Install git flow under Windows