Needs and benefits
The time of a git commit can be forged. So, it will be hard to prove that my git commit was having the correct time stamp. I do open source and I do live stream. If there is a copycat, who copied my code when I was doing live stream, forged an earlier timestamp of his/her git commit, and then blamed me as a copycat. It would be hard to say who was the actual copycat.
If there is a verified signature like github did, then people could know that the commit time was correct and the actual copycat will be able to be identified.
Feature Description
https://docs.github.com/en/authentication/managing-commit-signature-verification/displaying-verification-statuses-for-all-of-your-commits
The green "verified" label from the screenshot
image
A forgejo developer think that this can be done by adding an instance-key: https://forgejo.org/docs/latest/admin/signing/
forgejo/forgejo#4175
### Comment
### Needs and benefits
The time of a git commit can be forged. So, it will be hard to prove that my git commit was having the correct time stamp. I do open source and I do live stream. If there is a copycat, who copied my code when I was doing live stream, forged an earlier timestamp of his/her git commit, and then blamed me as a copycat. It would be hard to say who was the actual copycat.
If there is a verified signature like github did, then people could know that the commit time was correct and the actual copycat will be able to be identified.
### Feature Description
https://docs.github.com/en/authentication/managing-commit-signature-verification/displaying-verification-statuses-for-all-of-your-commits
The green "verified" label from the screenshot

A forgejo developer think that this can be done by adding an instance-key: https://forgejo.org/docs/latest/admin/signing/
https://codeberg.org/forgejo/forgejo/issues/4175