This release includes the culmination of several years of effort to allow you to customize our process to suit your specific needs. We’ve dropped a heavy dependency (
gli) and introduced a pretty slick DSL for creating new git commands or override our existing ones.
I am really excited to announce the released version 0.9.0 of the
Git-reflow’s default process isn’t meant to fit every team, which is why we’ve introduced
We’ve introduced a special file that can contain customizations to the default process. With this, you can:
1. Add hooks to be run before, or after any command
2. Use one of our pre-configured workflows as a basis for your own
3. Override any of the default commands
4. Create new commands
You can define a unique workflow for each of your projects simply by placing it in the root of your project, or by setting a special
reflow.workflow git-config setting with the full path of the file.
Here is an example showcasing all the various ways you can customize the process:
The block that you pass to each of the git-reflow reserved commands (
command) are executed in the context of our Core workflow class. This gives you the ability to use any code available to the
GitReflow module. We encourage you to use as much of GitReflow’s tooling as possible so that you can take full advantage of getting the current branch name, logging, exception-handling, colorized output, and several other features that are baked into GitReflow’s internals. For a full list of what’s available, see Available Workflow Helpers on our wiki.
Ramping Up To 1.0
With the re-workings of
Workflows in place, we’re getting ready for our first major release! Our current plans are to focus on:
- Introduce Pivotal Tracker & Trello workflows
- Add GitLab integration
- Add an Open Source workflow
We’re looking forward to some exciting times! We’d love to hear all the interesting ways you use these new workflows, so please don’t hesitate to let us know.