summaryrefslogtreecommitdiff
path: root/_posts
diff options
context:
space:
mode:
authortekkub <tekkub@gmail.com>2010-07-12 19:09:16 -0600
committertekkub <tekkub@gmail.com>2010-07-12 19:09:16 -0600
commit8bb4333a5ea527cc9b53edf509bb9f7c25e42350 (patch)
tree7c7d93e5f098f1f3f0ddd69d123a1feb8446c757 /_posts
parentc2ee51c311467177997cfd595f23ec656f1286f7 (diff)
Tweak the way we handle popular guides
Diffstat (limited to '_posts')
-rw-r--r--_posts/2009-09-09-removing-sensitive-data.textile2
1 files changed, 1 insertions, 1 deletions
diff --git a/_posts/2009-09-09-removing-sensitive-data.textile b/_posts/2009-09-09-removing-sensitive-data.textile
index f16b50c..185dfd2 100644
--- a/_posts/2009-09-09-removing-sensitive-data.textile
+++ b/_posts/2009-09-09-removing-sensitive-data.textile
@@ -2,7 +2,7 @@
layout: default
title: Removing sensitive data
description: Dealing with accidentally committed passwords or other sensitive information
-categories: popular, git_ninjutsu
+categories: popular git_ninjutsu
---
From time to time users accidentally commit data like passwords or keys into a git repo. While you can use @git rm@ to remove the file, it will still be in the repo's history. Fortunately, git makes it fairly simple to remove the file from the entire repo history.