4 ms·

You can simply ask “git log” to show you one coarse entry per Pr rather than “destroying” the more granular history

• deleted 3y ago
  [deleted]
• erik_seaberg 3y ago
  This. It bugs me that people permanently throw away details of changes rather than show just the log of merge commits.
  • hhjinks 3y ago
    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.
    • mablopoule 3y ago
      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.