EarJava@lemmy.fmhy.ml to Programmer Humor@programming.dev · 2 years agoApproved!lemmy.fmhy.mlimagemessage-square19fedilinkarrow-up144arrow-down10
arrow-up144arrow-down1imageApproved!lemmy.fmhy.mlEarJava@lemmy.fmhy.ml to Programmer Humor@programming.dev · 2 years agomessage-square19fedilink
minus-squareAsifall@lemmy.worldlinkfedilinkarrow-up0·2 years agoThat can lead to another problem though, which is that if a developer knows a merge is only part of the whole change, it becomes easy to assume any issues will be handled elsewhere.
minus-squarelearningduck@programming.devlinkfedilinkarrow-up1·2 years agoHow do you improve on this? 1 bigger PRs, but with multiple smaller commits, so reviews can review by commits?
That can lead to another problem though, which is that if a developer knows a merge is only part of the whole change, it becomes easy to assume any issues will be handled elsewhere.
How do you improve on this?
1 bigger PRs, but with multiple smaller commits, so reviews can review by commits?