3 ms·
Related question: Is there any risk to exposing .git if your Git repository is already publicly available (e.g. on GitHub)?
by Zarel 11y ago
Related question: Is there any risk to exposing .git if your Git repository is already publicly available (e.g. on GitHub)?
- fiatjaf 11y agoNo.
- viraptor 11y agoIf it's exactly the same repository - no. If it contains some extra branches with local changes, or potentially commits with private information / passwords - definitely. So in general - it's better not to have it in the first place, because it's unlikely that the person doing the commits knows the whole deployment strategy.
- skarap 11y agoIf you don't accidentally expose your credentials in .git/config to push changes to the repo (e.g. GitHub username/password for http auth) there is no risk. Still - having a real deployment process is much better. It could be as easy as extracting the contents of a tarball generated by git archive.