Andromxda 🇺🇦🇵🇸🇹🇼@lemmy.dbzer0.com to Programmer Humor@programming.devEnglish · 1 month agofuck the testslemmy.dbzer0.comimagemessage-square44fedilinkarrow-up11arrow-down10
arrow-up11arrow-down1imagefuck the testslemmy.dbzer0.comAndromxda 🇺🇦🇵🇸🇹🇼@lemmy.dbzer0.com to Programmer Humor@programming.devEnglish · 1 month agomessage-square44fedilink
minus-squareRamblingPanda@lemmynsfw.comlinkfedilinkarrow-up0·1 month agoThat’s what the pipeline is for. It’s not that hard to pinpoint the commit that lead to the errors.
minus-squarePsaldorn@lemmy.worldlinkfedilinkarrow-up0·1 month agoIf I rebase my branch with main I do not expect any failing tests. If you waste my time merging shit code, fuck you. Fix your shit. Unless prod is on fire and the CEO is prowling (even then, I’d argue standards should be maintained)
minus-squareRamblingPanda@lemmynsfw.comlinkfedilinkarrow-up0·1 month agoI don’t say this is good practice, you shouldn’t even be able to merge to main with failing tests. I’ve implemented an emergency flag to do this, but I don’t want to use it in normal, daily business.
That’s what the pipeline is for. It’s not that hard to pinpoint the commit that lead to the errors.
If I rebase my branch with main I do not expect any failing tests. If you waste my time merging shit code, fuck you. Fix your shit.
Unless prod is on fire and the CEO is prowling (even then, I’d argue standards should be maintained)
I don’t say this is good practice, you shouldn’t even be able to merge to main with failing tests. I’ve implemented an emergency flag to do this, but I don’t want to use it in normal, daily business.