In most cases it did: I even wrote a python script to use matplotlib to generate a few "contribution graphs" like one sees on github. That visual was usually enough to tell the profs to not give my teammates any credit when they didn't do diddly squat for code.

I learned most of the "defensive git" tricks during this time because I caught one of these guys trying to rewrite history to claim credit for my commit. That guy got referred to the university's "ya dun messed up bigtime" committee (I forget the actual title) and I think he was kicked out for academic dishonesty. Ever since then I gpg sign all my commits!

I was in a group project for a Psychology of Business class. This 4th string quarterback/son of a politician or some such just told us on the 1st day, "Well, considering we're graded as a group, I want to tell you I don't care what grade I get, so you guys are doing all of the work!"

> because I caught one of these guys trying to rewrite history to claim credit for my commit.

Great. It's one thing not to do anything (and get penalized for it accordingly) but trying to claim ownership is a whole new level.

There's an expensive way of protecting one's work: have an individual oral quiz on the code that was written.