Comment by yakkomajuri
2 years ago
Didn't know about all these (especially some flags) so thank you! I've personally used the bisect feature a lot to track down WTF bugs and git blame is essentially embedded into VSCode for me with the git extension, which also helps a ton.
For interactive blaming from command line, I can recommend `tig blame`: use the `,` binding for blaming the parent that introduced a change, and `<` to "go back".