3 ms·
but why should they? For example, you may have a rule that you need CI to pass to merge a branch to your trunk. But maybe CI is slow and flaky, and a business
by riffraff 6y ago
but why should they?
For example, you may have a rule that you need CI to pass to merge a branch to your trunk.
But maybe CI is slow and flaky, and a business test fails on a PR where you've only changed the README.
Sure, you can say "well, the rule is to only merge with green CI" and restart the failed job, but you can also think "well, I can merge this".
Maybe it's ok, maybe not, but I think you should trust your fellow developers with doing the right thing rather than berate them "you didn't follow the rules!"
Only a sith deals in absolutes.