Because they need merge commits to reliably track merges. I've seen merges without those merge commits not be properly tracked.
-
-
-
But why would you want a merge when you can have a ff?
-
Most of the time, you don't. But GitHub's brokenness means it can't reliably track fast-forward merges.
@GitLab does, though. -
In fact,
@GitLab has settings for enforcing fast-forward merges & not applying merge commits, even when merging from the web UI.
End of conversation
New conversation -
-
-
It may have sth to do with the fact that merging through the
@github website, a gratuitous merge commit is always inserted. idkThanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
I like
@gitlab approach better indeed.Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
They, for some reason, cannot hide the fact they love merge commits.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
I agree, though can depend somewhat on workflow. E.g. ready Trust Rust master is all merges. Works for them
-
S/Ready trust/Rust/. Thanks phone.
End of conversation
New conversation -
-
-
Welcome to my world!
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
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.