News for hackers. Stuff that matters.
Re:A GitHub repository was public-viewable by dreamcompiler on Friday March 04, 2022 @01:03PM (#30558135)
The clone issue is real, but it's no more complicated than it would be without git: Keep track of who has a copy of this data and where. Whatever system you have in place to solve that problem can also be used to manage the cloning process.

As for the individual repos, here's the procedure:

  cd <repo>
  rm -rf .git/  # DON'T TRY THIS AT HOME unless you know what you're doing.
  git add .
  git commit -m "Brand new repo"
Do not do the above unless you completely understand the ramifications. But those ramifications might be precisely the ones you want for legal compliance.
Re:A GitHub repository was public-viewable by JulianWasTaken on Friday March 04, 2022 @01:14PM (#30558273)
Please never do this -- not least of which because each person who does it will end up with now completely divergent histories and repos from each other.

There are various tools to properly filter history, e.g. `git-filter-repo`, but the short answer is as the grandparent commenter said, things get hairy, you need to rewrite history and coordinate. It's not a situation you should hope to get yourself into...

Re:A GitHub repository was public-viewable by guipsp on Friday March 04, 2022 @01:10PM (#30558230)
Might as well not use git then