Hey Strong, What would your proposed flow be for rebasing before PR? I agree it's much cleaner from a commit history standpoint. For me, I've never successfully managed to rebase anything without receiving merge errors for every commit replay. When you have a large feature branch that's touched a lot of code, manually merging each commit during the rebase is really painful. We've been using merge because from a developer perspective it "just works". If you have a strategy that has worked well for you in the past, I'm all for giving it a try.
Thoughts? Todd On Mon, Apr 21, 2014 at 9:14 AM, Strong Liu <[email protected]> wrote: > Hi guys, > > as $subject, rebase would give us a much much cleaner view to see what’s > happening :D > > it is really hard to trace the commit history, for example > > WDYT? >
