doc: modify the signing commit command

[CodeLeom]

Why:

The existing article instruct on how to sign a commit, but the provided command was wrong. I used the command, but it was not working until I was able to figure it out.

The existing command: git commit -S -m "YOUR_COMMIT_MESSAGE"

Correct command: git commit -s -m "YOUR_COMMIT_MESSAGE"

I also provided an additional context to why the signing might fail if the email on the local machine and remote (github) does not match.

Closes:

N/A

What's being changed (if available, include any code snippets, screenshots, or gifs):

Check off the following:

• I have reviewed my changes in staging, available via the View deployment link in this PR's timeline (this link will be available after opening the PR).

  • For content changes, you will also see an automatically generated comment with links directly to pages you've modified. The comment won't appear if your PR only edits files in the data directory.

• For content changes, I have completed the self-review checklist.

[welcome]

Thanks for opening this pull request! A GitHub docs team member should be by to give feedback soon. In the meantime, please check out the contributing guidelines.

[github-actions]

Automatically generated comment ℹ️

This comment is automatically generated and will be overwritten every time changes are committed to this branch.

The table contains an overview of files in the content directory that have been changed in this pull request. It's provided to make it easy to review your changes on the staging site. Please note that changes to the data directory will not show up in this table.

---

Content directory changes

You may find it useful to copy this table into the pull request summary. There you can edit it to share links to important articles or changes and to give a high-level overview of how the changes in your pull request support the overall goals of the pull request.

Source	Preview	Production	What Changed
authentication/managing-commit-signature-verification/signing-commits.md	fpt ghec ghes@ 3.14 3.13 3.12 3.11 3.10	fpt ghec ghes@ 3.14 3.13 3.12 3.11 3.10

---

fpt: Free, Pro, Team
ghec: GitHub Enterprise Cloud
ghes: GitHub Enterprise Server

[nguyenalex836]

@CodeLeom Thanks so much for opening a PR! I'll get this triaged for review ✨

[subatoi]

Hello again 👋 and thanks for your submission—

This is another case where I'd recommend raising an issue first in future, so we can figure out the best way to help you. -s is actually a different option and it isn't relevant here. If -S was/is failing for you when trying to follow this flow, then that suggests something is misconfigured in your setup. I'm afraid we're not equipped to help with that in this repo, but if your plan includes GitHub Support, you can reach out to them for help https://docs.github.com/en/support/contacting-github-support. As far as the other changes are concerned, once again I'm not sure how much this will actually help other users, as this page already links to https://docs.github.com/en/authentication/managing-commit-signature-verification/telling-git-about-your-signing-key

Thank you again for your interest in the GitHub Docs