summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authortekkub <tekkub@gmail.com>2010-03-03 01:50:44 -0700
committertekkub <tekkub@gmail.com>2010-03-03 01:50:44 -0700
commit14ff84d11dd0279d17a44832da1fe3b24c2698c8 (patch)
tree73ab808ee5721ad5783501256f3cd6aeb511ffbc
parent1884e6cf5a830abb2d269bd96c738d54aaf64de6 (diff)
That's ninjutsu too
-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 1d0b29b..bd8285a 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: repos
+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.