|
|
|
|
|
by ilyt
1060 days ago
|
|
Right but biggest projects out there like Linux kernel manage it just fine > The likelihood that a new commit lands on main before your tests finish is high, and restarting the process every time there's a new commit is time consuming. Merge queues are the only way to ensure that main does not break from conflicts that arise "in between" commits. But the code is still broken and still someone has to fix it ? That doesn't help in that. As for "broken main", how is just not allowing code that doesn't pass tests to merge to main not enough ? It all seems like a lot of complexity added because devs don't want to change shitty work practices... |
|