News for hackers. Stuff that matters.
Re:I Kind of Like Rebasing by AceJohnny2 on Friday June 21, 2024 @08:24PM (#40755183)
> After a rebase you have commits where no one's ever run the tests, no author ever intended to get the repo into that state. Hell, most likely no one knows if the code even compiles.

That is the role of the CI system.

Re:I Kind of Like Rebasing by lmz on Saturday June 22, 2024 @09:06AM (#40758868)
CI will usually only run the latest commit. Even if commit a, b, and c were all tested, the resulting commits a', b', and c' after rebase would usually only have the last one tested.
Re:I Kind of Like Rebasing by skybrian on Saturday June 22, 2024 @05:30PM (#40762383)
Since you shouldn't publish commits that weren't tested, this suggests you should publish only one commit at a time.

(Unless you think "works on my machine" is good enough testing. Sometimes it is.)

Re:I Kind of Like Rebasing by lmz on Saturday June 22, 2024 @09:13PM (#40763768)
So rebase then force push a', wait for CI, push b', wait for CI, push c'? Personally I just squash on merge.
Re:I Kind of Like Rebasing by account42 on Wednesday June 26, 2024 @07:17AM (#40798679)
And if you care about each commit always passing all test you should change your CI config accordingly.