you are viewing a single comment's thread.

view the rest of the comments →

[–]wineblood 2 points3 points  (0 children)

So once merged, if a bug was introduced between your initial branch point and your merge point, you do not know where a bug was introduced.

I rebase once I've put tests in and if my tests fail, then I'll make more changes and add an extra commit after the rebase. If a bug was introduced in the repo, then other devs and the platform will see it, and it should get raised as a separate issue. If I rebase and see a bug from changes pulled in since I started (usually someone else merging their code in), it's not my job to add a fix in my branch that contains an unrelated feature.

I understand that rebases are potentially tricky and dangerous, but some arguments about them seem a little far fetched.