3 ms·
On shared branches, I think the rules are different. Rebasing a shared branch is very sticky. But for single-dev branches, I think rebasing/forcing is fine -- d
by mmanfrin 11y ago
On shared branches, I think the rules are different. Rebasing a shared branch is very sticky. But for single-dev branches, I think rebasing/forcing is fine -- do what you want until it enters the main stream.
- brianwawok 11y agoSure but I think OP was advocating rebasing a shared branch so that git bisect would always pass on each commit
- setpatchaddress 11y agogit -f on a shared branch is a surefire way to lose commits. OMFG. It's better not to allow it at all. git revert will undo damage adequately, just not cleanly.
- brianwawok 11y agoYou usually won't lose commits with reflog, especially the more users of a repo the more reflogs.. but yes a disaster to go find them again...