My previous company was like this :25 devs, a single repo for all projectd, 2 branch per project (dev, prod). I was technical director and I saw difficulties rising in every project : lot of difference between the 2 branches (abandonned project, not compl ted refactoring), merge without conflict impossible (2 days needed for every big release)... The switch to git was very positive : you can create a lot of branch from master in just a few seconds so every new dev / refactoring is based on the last version of the production source code (master). There is many concept to learn with git but it's worth it.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
My previous company was like this :25 devs, a single repo for all projectd, 2 branch per project (dev, prod). I was technical director and I saw difficulties rising in every project : lot of difference between the 2 branches (abandonned project, not compl ted refactoring), merge without conflict impossible (2 days needed for every big release)... The switch to git was very positive : you can create a lot of branch from master in just a few seconds so every new dev / refactoring is based on the last version of the production source code (master). There is many concept to learn with git but it's worth it.