How to avoid the DCO check failing when making commits via the GitHub website?

[ghost]

(moving discussion of this topic over from the Discord thread)

The original issue that I reported was that the DCO check complained that my email address did not match the email address of the committing user when I made a new commit to an open PR via the GitHub website. 😕
https://github.com/autowarefoundation/.github/runs/5564534590

Earlier today I created another PR for the autoware-documentation project to update the README.md file with a sign-off included in the commit message but the DCO check has failed again. 😭

I understand that this problem can be easily avoided by making changes on my local machine and using git commit --amend -s, but is there a simple way to avoid DCO issues for commits made via the website? Was my sign off added incorrectly to the commit message?

[kenji-miyake]

@LalithVipulananthan Seeing these two PRs, it seems either the Author or Commiter should match the signed email address.
autowarefoundation/.github#9
autowarefoundation/.github#10 (I used git commit --amend for this.)

If you set your email public, you can select what email address to use for your commit.
autowarefoundation/.github#12

Or if you sign with the GitHub email address instead of the company one, the DCO check will pass.
autowarefoundation/.github#13

[kenji-miyake]

Or you can be sure there is no problem, you can force pass the DCO check by clicking this.

For example:

• Small docs changes probably don't have to be signed.
• You don't have to sign all commits because we squash them.
  • If there are multiple authors in one PR, it would be better to sign all commits to distinguish them.