Git Blame Alternatives

Discussions revolve around Git blame and similar tools like gitk, git-peek, and GitLens for inspecting code changes, commit history, and understanding past modifications in repositories.

➡️ Stable 0.6x DevOps & Infrastructure
3,867
Comments
19
Years Active
5
Top Authors
#6243
Topic ID

Activity Over Time

2008
7
2009
30
2010
46
2011
74
2012
155
2013
162
2014
204
2015
185
2016
238
2017
200
2018
215
2019
244
2020
342
2021
390
2022
330
2023
320
2024
328
2025
373
2026
24

Keywords

e.g CLI gitsense.com MichaelMure model.md github.com LICENSE URL GitHub API git commit blame commits repo log history git repo changed merge

Sample Comments

clktmr Jul 5, 2020 View on HN

You know that 'git blame' exists?

anshul Jan 20, 2010 View on HN

gitk already does that, doesn't it?

j1elo Jan 17, 2023 View on HN

You might find git-peek useful:https://github.com/jarred-sumner/git-peek

Icathian Jul 26, 2021 View on HN

Gitlens extension in vscode is quite good for this as well

em3rgent0rdr Jan 2, 2022 View on HN

git blame so the developer can remember why they did something 15 years ago.

dddddaviddddd Jan 23, 2019 View on HN

Not clear how this is better than a glance at the commit history.

frereubu Dec 24, 2021 View on HN

Sounds like a plain-language version of "git blame"!

petters Mar 4, 2021 View on HN

Git blame is helpful here. See e.g.https://github.com/git/git/commit/1b11b64b815db62f93a04242e4...

chris_wot Mar 4, 2021 View on HN

Because comments can be tedious and get out of sync with the repo. Why not check the git history? I wish more repos could be like this!

chopin May 17, 2022 View on HN

Git blame can be very embarassing....