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
-
Most of the colab vcs work I do is at work. The project is of a reasonable size where generally we agree on an API and then work on either side of it. So basically don't bother with branching unless we're really going to break something (rework). If API requirements change we sit a few meters away. Some people do work on branches, but tbh it's usually possible to do continuous integration.
Related Rants
It's not fake.
Really.
It's not.
Hello guys, I've got a question. When you're working with someone in a project using a VCS, how do you go when implementing stuff? Do you create a new branch and then merge to master or do you tell to the other guy that you're going to do "this thing" so he doesn't do it or what? I've never collaborated with someone and I would like to have a little information about this topic. The things I've built have been all by myself so If some day I ever plan to work with someone else I rather know this stuff already.
undefined
vcs
collaborating