Gusted a97de1d5bb [GITEA] Add noreply email address as verified for SSH signed Git commits ... - When someone really wants to avoid sharing their email, they could configure git to use the noreply email for git commits. However if they also wanted to use SSH signing, it would not show up as verified as the noreply email address was technically not an activated email address for the user. - Add unit tests for the `ParseCommitWithSSHSignature` function. - Resolves https://codeberg.org/Codeberg/Community/issues/946 (cherry picked from commit 1685de7eba) (cherry picked from commit b1e8858de9) (cherry picked from commit 1a6bf24d28) (cherry picked from commit 0122943345) (cherry picked from commit cc83614853) (cherry picked from commit 429febe0dc) (cherry picked from commit 58a9c2ebe9) (cherry picked from commit fef94aff1c) (cherry picked from commit 5c6ecd7579) (cherry picked from commit ffa33a82bf)		2024-01-22 18:13:40 +00:00
..
actions
activities
admin
asymkey	[GITEA] Add noreply email address as verified for SSH signed Git commits	2024-01-22 18:13:40 +00:00
auth
avatars
db
dbfs
fixtures	[GITEA] Add noreply email address as verified for SSH signed Git commits	2024-01-22 18:13:40 +00:00
forgejo/semver
forgejo_migrations
git
issues
migrations
organization
packages
perm
project
pull
repo
secret
shared/types
system
unit
unittest
user
webhook
error.go
fixture_generation.go
fixture_test.go
main_test.go
org.go
org_team.go
org_team_test.go
org_test.go
repo.go
repo_test.go
repo_transfer.go
repo_transfer_test.go