RE: Private vs Public Repos - Learning about GitHub

Really solid checklist, and the framing of "public is PUBLIC forever" is the part people underestimate the most. The point about git history exposing old commits even after a secret is deleted is something a lot of devs learn the hard way.

The nuance between "TODO in private" vs "trust problem in public" for the unimplemented storage backends is a great way to explain why the bar shifts once you flip that visibility switch, it's not about being finished, it's about not lying to strangers who'll never read the code.

Also appreciated the honesty about what wasn't done (no CI, no test suite, no dependency scanning), that kind of transparency is rare and useful in a tutorial.

Looking forward to the next post on other GitHub features! 💻

Greetings from the Marche countryside 🌿
@caparadiso