feat: private repositories #261

atproto doesn't have a concept of "private data" at the moment (we're working on it!), so even if you configured knot's git server to only work with authenticated users on the box, your issues and pull requests will still be public. not even sure if that's possible, honestly...it's just the way i'd think to secure a "bare" git server that doesn't have a fancy UI or anything.

Any change we can run a private knot server, not internet facing, and use it to host private repos? I'm all fine if issues are public as long as the content of the repo stays private

Our company is ready and willing to pay for a European private service.

Have there been any updates on protocol-level support for private data?