The solution I use to this issue, which I think is fairly straightforward, is to put any sensitive information such as credentials, or things that others don't

The solution I use to this issue, which I think is fairly straightforward, is to put any sensitive information such as credentials, or things that others don't care about such as aliases to company directories or running company-specific scripts, in a private repo. Then I put that repo as a submodule in my public repo. Anyone can look at or clone my public repo, but only I'll be able to initialize the submodule.