What changed is not, and has never been, a good pr description. The diff already tells us what changes.
What we need is why something was changed. I suspect this was a slip of the fingers, but for the avoidance of doubt: If anyone has approving PRs without a coherent “why” (and this includes digging deeper into the issue a PR fixes) stop: you’ve been doing this project a disservice. An issue thata or fixes is not a pass either. Often issues are created asking for something that doesn’t make sense, or without full understanding. Or the PR doesnt actually fix the issue > On 14 Jun 2026, at 16:53, Shahar Epstein <[email protected]> wrote: > > "I changed > X to fix Y... --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
