Need advice about which tool to choose?Ask the StackShare community!
Git vs Git Reflow: What are the differences?
What is Git? 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.
What is Git Reflow? Reflow automatically creates pull requests, ensures the code review is approved, and squash merges finished branches to master. Reflow automatically creates pull requests, ensures the code review is approved, and squash merges finished branches to master with a great commit message template.
Git and Git Reflow belong to "Version Control System" category of the tech stack.
Git and Git Reflow are both open source tools. It seems that Git with 28.1K GitHub stars and 16.3K forks on GitHub has more adoption than Git Reflow with 1.45K GitHub stars and 60 GitHub forks.
SVN is much simpler than git for the simple stuff (checking in files and updating them when everyone's online), and much more complex than git for the complicated stuff (branching and merging). Or put another way, git's learning curve is steep up front, and then increases moderately as you do weird things; SVN's learning curve is very shallow up front and then increases rapidly.
If you're storing large files, if you're not branching, if you're not storing source code, and if your team is happy with SVN and the workflow you have, I'd say you should stay on SVN.
If you're writing source code with a relatively modern development practice (developers doing local builds and tests, pre-commit code reviews, preferably automated testing, preferably some amount of open-source code), you should move to git for two reasons: first, this style of working inherently requires frequent branching and merging, and second, your ability to interact with outside projects is easier if you're all comfortable with git instead of snapshotting the outside project into SVN.
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
- Distributed28
- Small & Fast23
- Feature based workflow18
- Staging Area15
- Most wide-spread VSC13
- Disposable Experimentation11
- Role-based codelines11
- Frictionless Context Switching7
- Data Assurance6
- Efficient5
- Just awesome4
- Easy branching and merging3
- Github integration3
- Compatible2
- Possible to lose history and commits2
- Flexible2
- Team Integration1
- Easy1
- Light1
- Fast, scalable, distributed revision control system1
- Rebase supported natively; reflog; access to plumbing1
- Flexible, easy, Safe, and fast1
- CLI is great, but the GUI tools are awesome1
- It's what you do1
- Phinx0
Pros of Git Reflow
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 made8
- Awful merge handling5
- Unexistent preventive security flows3
- Rebase hell3
- Ironically even die-hard supporters screw up badly2
- When --force is disabled, cannot rebase2
- Doesn't scale for big data1
Cons of Git Reflow
Sign up to add or upvote consMake informed product decisions
What is Git?
What is Git Reflow?
Need advice about which tool to choose?Ask the StackShare community!
What companies use Git Reflow?
Sign up to get full access to all the companiesMake informed product decisions
What tools integrate with Git?
What tools integrate with Git Reflow?
Sign up to get full access to all the tool integrationsMake informed product decisions
Blog Posts
+7
+9
+4
+2
+3
+4
+5
+22