[pheis]

Or first thousand commits were squashed. First public commit tells nothing about how this was developed. If I were to publish something that I have worked on my own for a long time, I would definitely squash all early commits into a single one just to be sure I don't accidentally leak something that I don't want to leak.

[pheis]

>leak what

For example when the commits were made. I would not like to share publicly for the whole world when I have worked with some project of mine. Commits themselves could also contain something that you don't want to share or commit messages.

At least I approach stuff differently depending if I am sharing it with whole world, with myself or with people who I trust.

Scrubbing git history when going from private to public should be seen totally normal.

[kmaitreys]

Hmm I can see that. Some people are like that. I sometimes swear in my commit messages.

For me it's quite funny to sometimes read my older commit messages. To each of their own.

But my opinion on this is same as it is with other things that have become tell-tale signs of AI generated content. If something you used to do starts getting questioned as AI generated content, it's better to change that approach if you find it getting labelled as AI generated, offensive.

[kmaitreys]

Leak what?

[ecshafer]

If you have for example a personal API key or credentials that you are using for testing, you throw it in a config file or hard code it at some point. Then you remove them. If you don't clean you git history those secrets are now exposed.

[snovv_crash]

Timestamps