Exposing my writing in a public git repository after publication? I use private git repositories to manage the code I use for projects. After I publish a paper, I like to make the code available by making the repository public. My field is Geography/GIScience, and uploading code is typically not required for article submissions. I mostly refer friends/colleagues to this code and link the repositories from my website.

I also version control my manuscripts (typically an Emacs' .org file, .md, or a .tex file) within the same repository I use for the project. I find that its convenient to have the code and writing in the same repo since I code, write, and jot ideas simultaneously during a project. 

Are there any potential negative consequences of exposing my writing in these repositories too? Would it be seen as unprofessional? Are licensing issues with this? Is it a bad idea to include things like reviewers' comments and responses to reviewers in here? 

Is there a better approach for this? Would it be a good idea to use a submodule for writing that remains private even after I make the root repository public? I feel that this may be the way to go, but I also feel that submodules introduce some (unnecessary) complexity and I don't understand them well.
If you're like most people, you probably include comments in your tex files that may not be meant for public consumption: mistakes that you commented out, ideas for future projects that you don't want someone else to do before you, or general remarks that are a little too candid.

Some embarrassing examples are at https://twitter.com/overheardonaph, taken from tex source files submitted to arXiv.