Isn't this basically how Google works? Changes are committed directly to trunk as CLs (reviewed and tested before landing), using Blaze (Bazel) to speed up the CI.
Before AI, we didn't need to scale internal workflows like Google, but now with AI, we really need to learn how
Quote
@thorstenballOct 29
Thorsten Ball
Next question: why are you still using branches?
We talked about PRs. I don't think they make sense anymore, if you rethink them from first principles.
Yes, if you only use them to trigger CI, then sure, go ahead. That's a fat commit, not a PR. But for mandatory code review?
