They are working correctly. Branches were made to make people who weren't working together as a team able to collaborate and check each other code before putting it in.
A team of developers that work at the same location in the same codebase daily does not need branches, in fact, they are detrimental because it creates integration overhead and complicated builds.
As a frontend developer, I'm glad I didn't have to deal with the daily churn of Java code for system wide server level builds. But it is nice to pull a fresh copy from master to my local master to get me started for the day.
I just know that the master works. But we're also notified if the master has errors and are told not to pull.
How would you handle the case when you work on a task which takes let say four days. And it only will only work as a whole thing correctly? Dont push for four days? Give the testers a break for four days? How would you realize code reviews?
I think there is a reason why github and co has pull requests.
Also continuous deployment would be hard because in a team of 3+ people there would always be a incomplete thing in the code base
They are working correctly. Branches were made to make people who weren't working together as a team able to collaborate and check each other code before putting it in.
A team of developers that work at the same location in the same codebase daily does not need branches, in fact, they are detrimental because it creates integration overhead and complicated builds.
As a frontend developer, I'm glad I didn't have to deal with the daily churn of Java code for system wide server level builds. But it is nice to pull a fresh copy from master to my local master to get me started for the day.
I just know that the master works. But we're also notified if the master has errors and are told not to pull.
How would you handle the case when you work on a task which takes let say four days. And it only will only work as a whole thing correctly? Dont push for four days? Give the testers a break for four days? How would you realize code reviews?
I think there is a reason why github and co has pull requests.
Also continuous deployment would be hard because in a team of 3+ people there would always be a incomplete thing in the code base
Feature toggling.