5 ms·
I only use private repos, so that when my .ssh and .env leaks the public doesn’t see it. Probably. Maybe. Well…
by unsupp0rted 1y ago
I only use private repos, so that when my .ssh and .env leaks the public doesn’t see it. Probably. Maybe. Well…
- CER10TY 1y agoJust remember to go through your commit history if you ever plan on making that repo public.
- Normal_gaussian 1y agoI commonly flatten repos (by copy and create) when I share them. Its rare that the other person needs the commit history. I have often thought it would be nice to have a good tool to retroactively view and tidy them, but everything I've seen has not quite hit the nail on the head.
- unsupp0rted 1y agoI use the Pieter Levels commit history strategy of all my commit messages being the single word "commit" https://x.com/levelsio/status/1590908364393156608 https://x.com/levelsio/status/1590908364393156608
- thephyber 1y agoGit implemented a `.gitignore` file for this exact purpose. One of the first things to do when you create a new repo is to customize if for the language + OS.
- unsupp0rted 1y agoAnd .env is implemented for this exact purpose too, hand-in-hand with .gitignore ;) But mistakes happen all the item. It's very easy to fat-finger a line in .gitignore - one char off and you're toast.