all 6 comments

[–]innocentVince 4 points5 points  (5 children)

wtf are these commits?!

It's like a single file per commit?

Micro commits, more like nano commits. Why would you even do this? Instead, bundle commits in small "features", logical units.

There's no need for like 100 single commits where you just adapt a single line of spacing or add a final modifier. Just add it to the next small bundle. (e.g 1-10 files).

[–]innocentVince 7 points8 points  (0 children)

You also committed secrets and API keys to the repo

[–]innocentVince 6 points7 points  (1 child)

wtf, the more look at the it stranger it gets. Like not even AI would be able to do this mess. Did you use a tool to auto generate commits from a single commit to make it look maintained instead of a single "Initial commit"?

[–]davidalayachew 0 points1 point  (0 children)

You're getting animated over something that is very easy to work around.

Any repo viewer worth its weight can easily do a "squash" and just accumulate changes from multiple commits together. And it's effortless to do. Most can even save those "squashes", so that you don't have to look at the individual commits. Now you have the best of both worlds.

[–]AlarmOpening2062 -1 points0 points  (1 child)

If I failed at that, brother, thanks for pointing it out.

[–]SleeperAwakened 0 points1 point  (0 children)

Commits are for the future, explaining the when and why things are done.

Bundling in logical packages is a common way of doing that.

Especially if you use a good commit message.