30 ms·
I’m curious how they avoid pushing changes that break the build. Maybe they have some other reason that this doesn’t happen or is hard but having a large number
by dan-robertson 5y ago
I’m curious how they avoid pushing changes that break the build. Maybe they have some other reason that this doesn’t happen or is hard but having a large number of people trying to collaborate on a constantly broken repo is not a recipe for productivity.
I also wonder if there are typically 0 reviews or typically 1 — that is, are people even reading their own changes before they push them.
- ReleaseCandidat 5y ago> I’m curious how they avoid pushing changes that break the build. By not pushing changes that break the build. In other words: that does not work if you can't test (actually test, not just try to build) your code before pushing it to main.
- AlfeG 5y agoIs there anyone on the planet, that always run all tests locally even for last second minor change that definitely will not break a build? Especially funny for distributed around globe teams. When You spent half a day fixing a build issue from the "night" workers. Have eat a lot of this.