Rebasing to get a clean story is reevaluated. The best way if you want to keep a story is to simply merge, not rebase. That way, if you ever need to go back to reviewing, it's exactly the same as the one you tested during development. It also solves your problem about previously resolved merge conflicts.
If you do not care about saving the history, you can create a new branch from the wizard, check it, and then do git read-tree -u -m dev to update the working tree according to the dev branch. Then you can transfer everything into one large lock and combine it into a master as usual.
Karl Bielefeldt Jun 06 2018-11-11T00: 00Z
source share