The last company I worked at had every dev forking the repos they were working on, and then making PRs to the company repos. For me (being a messy brancher) that worked pretty good, nobody could see my mess, I obviously only committed clean working code, and the company branches were clean and few.
I like that approach. Sounds like it would work well with really large codebases
wait, you are posting an opinion about git branching and you never heard of forking? this, i think, tells us everything we need to know.
Of course I know what forking is but I never seen a company working that way.
We work like that in my company, this is a very good way for branching without messing with the main repositories branches 👍 Pull request in a lovely team, this makes all my days at work 😍
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.