> Of course you can do it like you said but that means longer feedback loops in general. If the team wants to integrate more often and reduce feedback loops the

> Of course you can do it like you said but that means longer feedback loops in general. If the team wants to integrate more often and reduce feedback loops then that model evolves. Longer feedback loops =/= long feedback loops. You can definitely wait 5 to 10 minutes if it means doing it right. > With the important mention that for small changes/fixes that needed to get deployed quickly nobody would bother with a branch they would just push to master. From my experience, the 1-2 lines fixes are the ones that benefit the most from automated CI because you’re doing it in a rush. In my team just last week a junior dev asked us to review their PR quickly because it was just 2 lines, and it didn’t even compile. We told them to be more careful in the future, but in the end it didn’t impact anything. It couldn’t possibly have impacted anything thanks to CI, it just makes it impossible to fuck up too recklessly.