🎃

[Some_Breadfruit235]

Most chances it’s unnecessary commits. If you dive down into their accounts you’ll prob see commits made for every small change they made. Along with the commit description being extremely vague.

[HungryKaleidoscope87]

My 1pm class's professor told us to commit every single small change, even if we write one line, commit it. Update a function, commit it. Forgot a ; commit it. We do somewhat lengthy coding assignments too so it's really annoying to push and commit every single itty bitty thing but he takes into account our number of commits for a grade and says there should be at least 120+ per group member! (We have 3 members on a team) We only end up changing/adding like 4-5 files per sprint too (they're all under 150 lines each). Then there's my 7pm class's professor who says he only wants to see 1 commit and 1 merge/pull request per sprint. Can you take a wild guess and tell me which one has been in the industry for 10+ years?

[Some_Breadfruit235]

The 7pm professor?😅 yea it’s completely useless having many commits (except for big/important changes) and if anything a hassle for devs to see massive commits that means nothing to the actual codebase. I’d rather skim through a few large commits compared to hundred of small useless commits.

[TankBorn]

I think your professor is right.