After two years of SVN we took the step we had been talking about: moving to Git. It wasn’t just a technical migration — it was a cultural change. And in retrospect, one of the best decisions we’ve made.
Why now¶
Merging in SVN had become more painful with every branch. BitBucket Server offers pull requests = proper code review. Offline work.
History migration¶
The git-svn bridge imported the complete SVN history including commits, authors and timestamps. An authors-file mapped SVN usernames to Git emails.
Git Flow¶
main branch (production), develop (integration), feature branches, release branches, hotfix branches. Feature branches are a given — creating and merging takes seconds.
Pull requests = Code review¶
Every change gets reviewed before merge. At least one reviewer approval required. Bugs are caught, knowledge spreads, the codebase is more consistent.
Cultural change¶
Local vs. remote commits, rebase vs. merge, staging area. The first month was painful. After a month, nobody wanted to go back.
Tips¶
- Use git-svn for history import. 2. Train the team. 3. Branch protection rules. 4. Mandatory pull requests. 5. Patience.
Need help with implementation?
Our experts can help with design, implementation, and operations. From architecture to production.
Contact us