diff options
| author | tekkub <tekkub@gmail.com> | 2010-07-12 19:09:16 -0600 |
|---|---|---|
| committer | tekkub <tekkub@gmail.com> | 2010-07-12 19:09:16 -0600 |
| commit | 8bb4333a5ea527cc9b53edf509bb9f7c25e42350 (patch) | |
| tree | 7c7d93e5f098f1f3f0ddd69d123a1feb8446c757 | |
| parent | c2ee51c311467177997cfd595f23ec656f1286f7 (diff) | |
Tweak the way we handle popular guides
| -rw-r--r-- | _posts/2009-09-09-removing-sensitive-data.textile | 2 | ||||
| -rw-r--r-- | index.markdown | 4 |
2 files changed, 3 insertions, 3 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. diff --git a/index.markdown b/index.markdown index 3342be8..bc94738 100644 --- a/index.markdown +++ b/index.markdown @@ -31,10 +31,10 @@ Popular guides -------------- <dl> - {% for post in site.posts reversed %}{% if post.categories contains "popular" %} + {% for post in site.categories.popular reversed %} <dt><a href="{{ post.url }}" id="{{ cat }}">{{ post.title }}</a></dt> <dd>{{ post.description }}</dd> - {% endif %}{% endfor %} + {% endfor %} </dl> Getting help |