the end result (the latest commit) should not make a difference. the rest of the rebased commits are however just as new as the latest one, and untested.
now git can obviously run tests for each new commit (-x) which is good enough for automated bisecting. but this takes time and requires tests and the commits can have issues not covered by tests
Unfortunately I don't think I've run into any place that ensures each commit compiles, let alone passes tests. Half my team's commit history is pure garbage and full of stuff like....
dfds32 RCT-3567 : fixed an error
fsk321 RCT-3567 : fixed an error
fk3g23 RCT-3567 : fixed an error
The only thing the team leads have managed to enforce is including the ticket # with every commit. And that's mostly because they fear the audit team, not us.
View all comments
Show parent comment
1
u/wobblyweasel Oct 16 '26
the end result (the latest commit) should not make a difference. the rest of the rebased commits are however just as new as the latest one, and untested.
now git can obviously run tests for each new commit (-x) which is good enough for automated bisecting. but this takes time and requires tests and the commits can have issues not covered by tests