Adds the 'git hf' Git extension to provide high-level repository operations for DataSift's HubFlow branching model, which is based on Vincent Driessen’s original blog post. See also: WebSharks Flavor Changes.
Mac via Homebrew (recommended)
brew tap websharks/formulas
brew install websharks-hubflowgit clone https://github.com/websharks/hubflow.gitcd hubflow&&git checkout mastersudo ./install.sh
Windows users will need something like Cygwin in order to use this extension.
Upgrading to the latest version of the HubFlow tools is very easy:
Mac via Homebrew (recommended)
brew update
brew upgrade websharks-hubflowsudo git hf upgrade
See our tutorial website to learn more about the GitFlow branching model and how to use the HubFlow tools.
To see what's new in each release, see our Changelog.
- Added support for an additional synchronized repo that rides with the primary.
- Added a scan for an existing
devbranch; if it exists we use this over the default name:developfor the "next release" branch.
To enable the synchronization functionality (i.e. if you have both a lite/pro version you are maintaining together); use the s flag.
From your repo directory...
$ git hf init -asf
From your repo directory...
$ git hf init -asf
... just fill in the blanks where it asks for your configuration. Most of it can just be left with the default values. To clarify, there are three flags here. a = ask for configuration values, s = enable synchronization functionality (optional), and f = force a new set of config values, overriding any that already exist. I recommend always using these flags together; i.e. git hf init -asf
NOTE: If you enable the s flag (synchronization) you will be asked for two config sets. That's normal. In synchronization mode all of your commands are duplicated across two repos.
Once you are configured, you can do this...
$ git hf feature start 123
... where 123 is a GitHub issue that is connected to a feature branch.
HubFlow is published under the liberal terms of the BSD License, see the LICENSE file. Although the BSD License does not require you to share any modifications you make to the source code, you are very much encouraged and invited to contribute back your modifications to the community, preferably in a Github fork, of course.