summaryrefslogtreecommitdiff
path: root/_posts/2009-09-09-removing-sensitive-data.textile
diff options
context:
space:
mode:
authortekkub <tekkub@gmail.com>2010-07-12 19:05:59 -0600
committertekkub <tekkub@gmail.com>2010-07-12 19:05:59 -0600
commitc2ee51c311467177997cfd595f23ec656f1286f7 (patch)
tree02d781853b8692f376c1be4ce4b70738fb77faf7 /_posts/2009-09-09-removing-sensitive-data.textile
parentf985030efd5c7c4b8445265613a6274c182aff3e (diff)
Handle spacey category names differently
Diffstat (limited to '_posts/2009-09-09-removing-sensitive-data.textile')
-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 bd8285a..f16b50c 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.