Re:Julia Evans: Git rebase, what can go wrong
by joshribakoff on Monday November 06, 2023 @01:28PM
(#38166618)
You can simply ask “git log” to show you one coarse entry per Pr rather than “destroying” the more granular history
[ Parent
| on HN ]
Re:Julia Evans: Git rebase, what can go wrong
by erik_seaberg on Monday November 06, 2023 @02:45PM
(#38167855)
This. It bugs me that people permanently throw away details of changes rather than show just the log of merge commits.
Re:Julia Evans: Git rebase, what can go wrong
by hhjinks on Monday November 06, 2023 @03:30PM
(#38168537)
Why would I want to keep the details? Umpteen "tmp", "fix" and "fixed typo" provide negative value. When I check the blame of a line, I need to see the context of the change, meaning a description of all the work that was done as part of that change, and perhaps a ticket number. Anything else is noise that actively detracts from the value of the log.
It's like 4K porn. It's less appealing when you see everything.
Re:Julia Evans: Git rebase, what can go wrong
by mablopoule on Monday November 06, 2023 @03:42PM
(#38168685)
No yeah, absolutely do squash those commits, they are actually polluting the git history.
The issue for me is when commit who are about adding a new value in the env file become mixed with template and responsive handling, mixed potentially with a bug fix.