4 ms·
It matters because when I: * use filtering commands like "git log -S" * press the "annotate" button in my IDE and can see which commit introduced each line *
by nemetroid 3y ago
It matters because when I:
* use filtering commands like "git log -S"
* press the "annotate" button in my IDE and can see which commit introduced each line
* run "git bisect"
* use "tig" to drill down through the history of a file (shortcut "," is "move to commit preceding current line's blame commit")
...every step of the way, I get a meaningful description of why a change was made and what other diffs were necessary to achieve that change. And not just "fix", "bug", "PR commments".
- nomel 3y ago> * press the "annotate" button in my IDE and can see which commit introduced each line In PyCharm, I can see which commit introduced each line, regardless of branching. Same with drilling down through a files history. Is this an IDE limitation you're seeing? > every step of the way, I get a meaningful description of why Isn't this more about commit messages, than anything else?
- nemetroid 3y agoThe context of my comment is the usefulness of a clean history, not about merging vs rebasing. > Is this an IDE limitation you're seeing? I'm using Jetbrains too.
- WorldMaker 3y ago* `git log --first-parent -S` * `git blame --first-parent` * `git bisect --first-parent` * At least one "tig-like" with a --first-parent first UI: https://github.com/kalkin/git-log-viewer https://github.com/kalkin/git-log-viewer
- seba_dos1 3y ago--first-parent is incredibly useful, but having both merge commits and properly curated atomic commits under them is even more useful.