From 2c281baf00bafb9a10b65f9f1e92a370edfc6661 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Mon, 27 Feb 2017 16:18:20 -0400 Subject: [PATCH] better headings --- doc/tips/using_signed_git_commits.mdwn | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/doc/tips/using_signed_git_commits.mdwn b/doc/tips/using_signed_git_commits.mdwn index 6ae749334d..cf1b744c8a 100644 --- a/doc/tips/using_signed_git_commits.mdwn +++ b/doc/tips/using_signed_git_commits.mdwn @@ -6,7 +6,7 @@ is the same data that was originally commited to it. This is recommended if you are storing any kind of binary files in a git repository. -## How to do it +## Configuring git-annex You need git-annex 6.20170228. Upgrade if you don't have it. @@ -21,6 +21,8 @@ But, any existing clones will not, so this should be run in them: git config annex.securehashesonly true +## Signed commits + It's important that all commits to the git repository are signed. Use `git commit --gpg-sign`, or enable the commit.gpgSign configuration.