forgejo/models
Gusted 1a6bf24d28
[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)
2023-11-27 18:28:00 +01:00
..
actions
activities
admin
asymkey [GITEA] Add noreply email address as verified for SSH signed Git commits 2023-11-27 18:28:00 +01:00
auth [GITEA] Drop sha256-simd in favor of stdlib 2023-11-27 18:28:00 +01:00
avatars
db [GITEA] Add slow SQL query warning 2023-11-27 18:27:35 +01:00
dbfs
fixtures [GITEA] Add noreply email address as verified for SSH signed Git commits 2023-11-27 18:28:00 +01:00
forgejo/semver
forgejo_migrations [SECURITY] Rework long-term authentication 2023-11-27 16:17:05 +01:00
git
issues [FEAT] allow setting the update date on issues and comments 2023-11-27 16:16:02 +01:00
migrations [GITEA] Drop sha256-simd in favor of stdlib 2023-11-27 18:28:00 +01:00
organization
packages
perm
project
pull
repo [GITEA] Improve HTML title on repositories 2023-11-27 18:27:35 +01:00
secret
shared/types
system
unit
unittest
user [GITEA] notifies admins on new user registration 2023-11-27 18:27:36 +01:00
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