Hacker News new | ask | show | jobs
by kadoban 79 days ago
Git doesn't do that. People needlessly destroying history do that.

Git will happily let you merge branches and preserve the history there. GP seems to like that history being in PRs only on github instead. I don't get why, that just seems worse to me.

2 comments

The why is that most people when given the merge option don’t clean up their history so you end up with tons of garbage fix up commits.
That is an issue of ignorance, not laziness. It’s not obvious at all to an average developer that only uses `add/commit/merge/fetch/push/pull/rebase/restore/reset` that they can manipulate their change history.
The cause stops mattering after a while, either you have to go on a full time campaign to educate people… or switch the setting to rebase and squash and be done with it.
Off-topic, but what does GP stand for? I know OP usually means Original Poster, but I'm not familiar with GP.
Grand-parent, as-in the parent of my parent comment.