Chatting about History and Blame (GitHub)

So as I understand it, History is more bare bones than Blame, listing only the dates something was changed, but not what was changed. For me, blame seems more useful for now, as it seems a nice way to review my code development and also a good tool to help me fix errors.
I will certainty try to remember this! Working alone right now, but it seems even more helpful when working with multiple people, to keep oversight.

What do others here think:)?

1 Like

What exactly is Blame?

Its a function in Github where you can see who added certain lines to a script (or removed them) and when. So you know when something goes wrong, you can look back and see whats added what might cause the error.

I got the same impression, history just shows the different commits, allowing you to get the files at that point in time and look at them. Then blame lists line for line in which commit they did get changed for the last time and who did it, allowing you precisely to “blame” whoever made a mistake in the code.

Two things that I found interesting though. Combining history and blame let’s you check the dates in blame and get a feel on how the file developed over time without having to look at the multiple versions. The second one is that, in blame view, you can click where I’m showing in the screenshot


and change the blame view to the one prior to a particular change. This way you can figure out how particular pieces of code evolved over time and who did the changes (the first blame view just shows who did the last change). Pretty handy!!

Privacy & Terms