From 206a1d16fe5a8e1aff2a943bc0c9b92c86a78ce1 Mon Sep 17 00:00:00 2001 From: Shekhar Chauhan Date: Thu, 14 Jul 2022 13:00:46 +0530 Subject: [PATCH] Update signing-commits.md --- .../managing-commit-signature-verification/signing-commits.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/authentication/managing-commit-signature-verification/signing-commits.md b/content/authentication/managing-commit-signature-verification/signing-commits.md index a158f5199a66..79484750820d 100644 --- a/content/authentication/managing-commit-signature-verification/signing-commits.md +++ b/content/authentication/managing-commit-signature-verification/signing-commits.md @@ -34,9 +34,9 @@ You can also manually configure [gpg-agent](http://linux.die.net/man/1/gpg-agent If you have multiple keys or are attempting to sign commits or tags with a key that doesn't match your committer identity, you should [tell Git about your signing key](/articles/telling-git-about-your-signing-key). -1. When committing changes in your local branch, add the -S flag to the git commit command: +1. When committing changes in your local branch, add the -s flag to the git commit command: ```shell - $ git commit -S -m "your commit message" + $ git commit -s -m "your commit message" # Creates a signed commit ``` 2. If you're using GPG, after you create your commit, provide the passphrase you set up when you [generated your GPG key](/articles/generating-a-new-gpg-key).