Need advice about which tool to choose?Ask the StackShare community!
Git vs Git Flow: What are the differences?
Developers describe Git as "Fast, scalable, distributed revision control system". Git is a free and open source distributed version control system designed to handle everything from small to very large projects with speed and efficiency. On the other hand, Git Flow is detailed as "A set of git extensions to provide high-level repository operations". It provides excellent command line help and output. It is a merge based solution. It doesn't rebase feature branches.
Git can be classified as a tool in the "Version Control System" category, while Git Flow is grouped under "Git Tools".
Git and Git Flow are both open source tools. It seems that Git with 28.2K GitHub stars and 16.3K forks on GitHub has more adoption than Git Flow with 1.9K GitHub stars and 455 GitHub forks.
According to the StackShare community, Git has a broader approval, being mentioned in 3934 company stacks & 4790 developers stacks; compared to Git Flow, which is listed in 9 company stacks and 4 developer stacks.
Pros of Git
- Distributed version control system1.4K
- Efficient branching and merging1.1K
- Fast959
- Open source845
- Better than svn726
- Great command-line application368
- Simple306
- Free291
- Easy to use232
- Does not require server222
- Distributed27
- Small & Fast22
- Feature based workflow18
- Staging Area15
- Most wide-spread VSC13
- Role-based codelines11
- Disposable Experimentation11
- Frictionless Context Switching7
- Data Assurance6
- Efficient5
- Just awesome4
- Github integration3
- Easy branching and merging3
- Compatible2
- Flexible2
- Possible to lose history and commits2
- Rebase supported natively; reflog; access to plumbing1
- Light1
- Team Integration1
- Fast, scalable, distributed revision control system1
- Easy1
- Flexible, easy, Safe, and fast1
- CLI is great, but the GUI tools are awesome1
- It's what you do1
- Phinx0
Pros of Git Flow
Sign up to add or upvote prosMake informed product decisions
Cons of Git
- Hard to learn16
- Inconsistent command line interface11
- Easy to lose uncommitted work9
- Worst documentation ever possibly made7
- Awful merge handling5
- Unexistent preventive security flows3
- Rebase hell3
- When --force is disabled, cannot rebase2
- Ironically even die-hard supporters screw up badly2
- Doesn't scale for big data1