On the other side there's people that genuinely use that as an excuse and say "they'll open source after they cleaned up the code". Why they couldn't clean it up in the clear is beyond me, no one will shame you for your code, just sharing it under a free license is admirable in and of itself
Those are the kind of people who will always find something to ridicule or complain about, though, so you should never let their hypothetical bitching affect your decisions.
I was watching a YouTuber going over a major revision update for a framework or something and he said "I skipped over the part where I was coding this" nah dude, I wanna see that as well. What did you try and how did it go.
Asshole take: if you share your project online but not the source code I immediately think your code sucks.
Let's be real your clone project is not something a venture capitalist is going to invest in, there's literally no reason to hide it but shame. Shame of sinful and bad code.
This applies to any project, really. At my workplace, if someone refuses to let other teams look under the hood of a product, 95% of the time, it's because their code is absolute garbage, but their leaders didn't want to wait so they pushed it to prod and now it's up to some junior employee to fix all the shit that blows up in prod.
And just for closure, 5% of the time, it's because there actually is no product at all.
I have a private repo on GitHub that is private for this reason. I made it in a weekend for fun, and it's honestly so bad. I have spent way longer fixing dumb mistakes that I spent developing the main features in the first place. But I learned a lot while doing it (and fixing it), and my current project that I'm working on is much, MUCH better. I do have it in a public repo.
Specifically OpenBSD. If you browse into the Windows System32 folder you'll eventually trip over an etc directory... inside you'll find a file called hosts.