Yeah that's pretty much what everybody says when you make an argument to stop rebasing.https://twitter.com/triketora/status/909016603450363905 …
-
-
I end up pushing a lot of garbage to branches basically as a backup system. Nobody needs to see that in a year.
-
I also might be crazy, but I find the rebase workflow can be pretty nice for dealing with interim changes to master.
-
Maybe it's Stockholm syndrome?
-
FWIW, I think that a large open source project and a large team building a product are different contexts.
-
We frequently talk about many varied activities as if they are similar enough to warrant the same processes.
-
I get that ppl are trying to solve real problems with rebase. I don't think everybody has those such that it should be standard practice.
-
I don't find "tidy" to be a persuasive argument in general.
-
Sure it is. Have you met developers?

- 1 more reply
New conversation -
-
-
we use the exact same open source fork model for my team (4 engineers) and rest of the teams started embracing. what about rebase? >>
-
we rebase our fork's branches regularly then push a PR, which we squash without a merge-commit. we bisect maybe once/twice, didn't fail us
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
