4 ms·
> I learned a valuable lesson here though. Don’t trust .gitignores and gems like Firago for keeping your data safe. Open source is awesome, but if you are deali
by riquito 12y ago
> I learned a valuable lesson here though. Don’t trust .gitignores and gems like Firago for keeping your data safe. Open source is awesome, but if you are dealing with anything that can be scaled up to thousands of dollars per hour – at least store it in a private repo if not on your local machine.
You learned the wrong thing :-P The lesson here is "always check what you're committing"
- jrochkind1 12y agoThat and: Immediately invalidate any auth information that was accidentally published, no matter how briefly. I realize I haven't always followed this advice myself. So the reminder from the OP story is useful.
- fein 12y agoAs an additional layer of safety, you can also commit to a local repo, or a private bitbucket repo, and give it all a nice once over before pushing everything to GH. At least this keeps your screw ups out of public scope.
- zo1 12y agoIsn't that what you're doing anyways when you use a DCVS? Granted, I use mercurial. It has two components on your side, your working directory, and the actual repo. Committing moves changes from your working directory, and saves them to a branch on your local repo. Then you get the local repo to push that change to a remote one. In essence, "committing" then is the act of pushing your changes to your local repo. Or you could, you know, just look at the changes on disk if really required.
- coldpie 12y agoYes, that's how Git works. I'm not sure what fein meant.