Ask HN: How do you reconcile private repos and having a good GitHub portfolio?
Most of my personal projects are big full stack things that I put onto the App Stores and they handle loads of user data, and usually I like to keep those locked in private repositories because, well, that's what I do with all my projects. (Feel free to point out how that's bad, but I think it feels weird to throw commits at a public repository for a side project, and it actually makes me not continue with them for some reason)
Most places ask to see your GitHub, and with the exception of one really simple fork and issue fix, mine's just "empty" looking.
In reality there's like ten trillion lines of code everywhere, and fully complete projects there, some of which usage.
Shouldn't there be some way to open your repositories temporarily to employers or something? How do you reconcile this?