git-flow tells you what branches should exist. Jitly actually creates them and ties them to your ticket.
git-flow is a branching model — develop, feature/, release/, hotfix/, main. It's a set of rules about which branch to cut from and where to merge back. A lot of teams still follow some version of it even if they don't use the actual git-flow CLI extension anymore.
Jitly isn't a branching model at all. It doesn't care if you use git-flow, trunk-based dev, or something you made up. It just automates whatever convention you already picked and connects it to Jira.
You can literally set your Jitly branch template to match git-flow: feature/{ticket_lower}-{desc} pulls from develop, and Jitly handles the pull + create + checkout for you every time, so nobody has to remember the rule.
| git-flow | Jitly | |
|---|---|---|
| Defines branch types | Yes | No, uses your template |
| Creates branches for you | Partially (CLI extension) | Yes, tied to ticket |
| Updates Jira | No | Yes |