Divversion

Divversion

Git. Automated.

8 followers

Divversion makes it easy to work together on code, with automatic file merges, powerful conflict resolution, and seamless file versioning. Based on Git and plays nice with GitHub, Bitbucket, GitLab!
Divversion gallery image
Free Options
Launch Team / Built With
Intercom
Intercom
Startups get 90% off Intercom + 1 year of Fin AI Agent free
Promoted

What do you think? …

Klaus Wernigerode
Hi Everyone! I'm super excited to let you know about the product we have been working on hard here for the last couple of months. It all started with yet another super-painful Git merge conflict in the company I was working on at the time... Yes, good Git hygiene can prevent all of these problems, but in the hectic world of startup coding, we forgot to brush our teeth... And why not automate all this? So we did. The result is called Divversion and it makes it easy to work together on code, with automatic file merges, powerful conflict resolution, and seamless file versioning. Based on Git and plays nice with GitHub, Bitbucket, GitLab! In a nutshell, it combines the best of file sharing (quick syncing) with the power and versatility of Git version control, giving you the best of both worlds in an easy-to-use package. It even has a much more powerful merge engine than Git itself. I could waffle on here for a while about why this is cool, but it's really best to try it out yourself - just download the free app at https://www.divversion.com and give it a spin. There are also complete tutorials at https://docs.divversion.io if you prefer to read a bit first. Thanks for reading and DM me if you have any questions! Klaus
Samuel Parker
Hey Klaus, this sounds super useful! I can't count how many times I've been stuck dealing with merge conflicts, so something like Divversion could save a ton of headaches. Just curious, does it integrate smoothly with existing Git workflows? Congrats on the launch!😄
Klaus Wernigerode
@samuelparker Totally. After you initialize a repo (which creates just one extra 'config' branch to keep some metadata), nothing else changes. You can use it just for one feature branch at a time and then merge back into main with a PR when you are done. It's designed to play nice with standard Git. If there are any problems, let us know and we'll fix it.