Hey, great question. I have never used InteliJ however from my understanding of git blame. It gives you line by line the commit history of a specific file. So that could be helpful if you know or have an idea of where a bug or defect could have been introduced, just scan the file and find it. However, if on your branch you have made updates to multiple files and are not sure where the bug could have come from. Then git bisect will help by allowing you to quickly see the outcome of your code by going through commits for you. So like I mentioned in the article it might be more useful when you are doing front end / ui work and want to visually see changes.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
How does this compare to git blame command, that one seems simpler, at least through InteliJ?
Hey, great question. I have never used InteliJ however from my understanding of
git blame. It gives you line by line the commit history of a specific file. So that could be helpful if you know or have an idea of where a bug or defect could have been introduced, just scan the file and find it. However, if on your branch you have made updates to multiple files and are not sure where the bug could have come from. Then git bisect will help by allowing you to quickly see the outcome of your code by going through commits for you. So like I mentioned in the article it might be more useful when you are doing front end / ui work and want to visually see changes.