On 05/07/2021 15:02, Randall S. Becker wrote:
I do not want anything helping out the use of rebase, which we in our shop - except for rebase --autosquash to fix up topic branches for delivery.
I was wondering what the background/context to the 'actively discourage'
is?
I'd have expected that some in-place rework (i.e. rebase) could happen
before code review, with possible further rework beyond simple
fixup/squash commits being possible after review (if demanded), but with
the same fork-point (rather than following movements in the 'upstream'),
rather similar to Git's development. i.e. Is it that the fork-point
shouldn't be moved without good reason and permission, or something else?
just wondering...
--
Philip