Git Feature Branch Tooling.

Why it's awesome

The core idea behind the Feature Branch Workflow is that all feature development should take place in a dedicated branch instead of the master branch. This encapsulation makes it easy for multiple developers to work on a particular feature without disturbing the main codebase. It also means the master branch will never contain broken code, which is a huge advantage for continuous integration environments.

-- Inspired by Git Feature Branch Workflow (@atlassian).

Getting Started

Install with Homebrew

$ brew install gitfit

Install with npm

$ npm i -g gitfit

Install with Yarn

$ yarn global add gitfit

Run with npx (without installing)

$ npx gitfit <command> [<options>]

Usage

Usage:

	$ gitfit <command> [<options>]

Options:

	-h, --help              Display help information
	-v, --version           Output version
	init                    Initializy repository
	start                   Start new feature branch
	finish                  Finish feature branch
	publish                 Publish master branch or feature branch

Examples:

	$ gitfit init
	$ gitfit start <feature-name>
	$ gitfit finish <new-tag> [<main_branch>] # default: master
	$ gitfit publish [<remote-branch>]  # default: current branch

Contributing

Want to contribute? Follow these recommendations.

License

Designed with ♥ by CJ Patoilo. Licensed under the MIT License.