schalkneethling@programming.dev to Programming@programming.dev · 11 months agoGit Thingsmatklad.github.ioexternal-linkmessage-square8fedilinkarrow-up136arrow-down114cross-posted to: git@programming.dev
arrow-up122arrow-down1external-linkGit Thingsmatklad.github.ioschalkneethling@programming.dev to Programming@programming.dev · 11 months agomessage-square8fedilinkcross-posted to: git@programming.dev
minus-squarethemusicman@lemmy.worldlinkfedilinkarrow-up2·11 months agoQuite the opposite. If you fast forward merge without squashing, you lose the ability to meaningfully bisect, since only the head of each merge is checked by CI - other commits may not even build
minus-squaresnowe@programming.devMlinkfedilinkarrow-up1·11 months agoMy point was about merging in general. Unless you’re either Making sure every single commit builds Squashing and merging, with no merge commit Then you’re not going to be able to effectively use git bisect.
Quite the opposite. If you fast forward merge without squashing, you lose the ability to meaningfully bisect, since only the head of each merge is checked by CI - other commits may not even build
My point was about merging in general. Unless you’re either
Then you’re not going to be able to effectively use git bisect.