As detailed in "Can open source code hosted at github be closed-source?":
GitHub itself has nothing to do with how you license your code. So you can decide to stop publishing your source via GitHub, but everything that has been forked and cloned from it up to that point is of course still "out there" under the open source license you originally used.
So it is more about:
- accessibility: does it matter that everyone can access/read your code?
- licensing: what kind of license do you attach to the content of that repo?
I prefer keeping separate:
- template files (the equivalent of your Lorem Ipsum files)
- script files able to generate the actual valued files
from the value files themselves (the files with the actual "company" data).
I store those ones away from GitHub.
That way, I can declare a content filter driver which, on checkout, will automatically generate the final files for me.
(See "Automatically ignore selected code changes when pushing to a git-hub repository" for more)
