Migration from SVN to Git
SVN has been used by RichBrains’ tech leaders and developers for over 3 years now and proved itself to be quite a good version control system to handle projects of any size.
However, recently RichBrains development team has decided to switch to Git. It was mainly team’s motivation that played a considerable role in starting work with Git, as it has matured a lot since its first creation.
Thus, we chose Git due to a number of its obvious advantages:
- It’s distributed: Git allows developers to commit issues even when they are not online and have a full change history.
- Easy branching and merging: Git supports rapid branching and merging and has robust tools to navigate through non-linear development history.
- Speed and scalability: Git perfectly handles big-sized projects with long history, and it’s faster than many other version control systems.
- Attractive and extremely user-friendly toolkit design.
It took the development team 1 day to move all projects to Git. The biggest pitfall was inconsistent usage of branches/tags/trunk comparing to “standard” SVN structure, so to write a simple script wasn’t enough to make the conversions.
So, as for now, Git cannot be considered a SVN substitution. It’s neither better nor worse; it’s just a different system with its unique functions, which can be considered as a reason for its usage.To stay informed about the latest company news, keep track of the updates in our press-room.


