Ranter
Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Comments
-
If it is small team, small project or you need only one deployment, I don't see why not using only master branch.
Who bothers himself with branches, merges, cherry pick commits and stuff? Just use it to share code.
Welcome btw. -
They are probably just maturing away from a shared drive, SharePoint, or from the "checkout" (Visual Source Safe) kind of source control.
-
dieterdw2318yWe push our base project to master. Other branches are for enhancements to the project before we sync it to the master. Took us 6months before we starten using another branch :p
Also ; only 2 devs -
quispy1238yWe do this and will probably never change but it's leagues ahead of CVS and having to notify everyone to stop checking in while you check in one file at a time.
-
zshh38538yWe did that at my previous company. It worked fine, but I was the only one even close to being junior. Everyone else was much older and had worked with code for a long time.
But we very rarely had someone check something in that fucked things up.
I just joined a company where all push to master branch. 🙄
undefined