> Explain why you think making a single commit is related to any source code sharing obligation?

When you share code it's presumably for people to use. It is often useful to have commit history to establish a few things (trust in the author, see their thought process, debug issues, figure out how to use things, etc).

> You completely failed to establish why making a single commit is indicative of it being garbage.

A single commit doesn't mean it's garbage. It erodes trust in the author and the project. It makes it hard for me to use the code, which is presumably why you share code.

My garbage code response was in regards to the growing trend to code (usually with ai) some idea, slap an initial commit on it and throw it on GitHub (like using a napkin and tossing it in the rubbish bin).

Here's the thing, get used to single big commits. Eventually, somebody is going to try to train on specific change sets. This'll enable models to learn specific authors mannerisms, idiosyncracies etc... Single large commits creates an info asymmetry boundary, which is about the only defense a creator has in a world of willful infringement to train algorithms to replace or devalue them in the market. It sucks... But this is the world we're growing into now.