problem with assigning users.noreply.github.com fake email adresses #12

When migrating repos from github, to have commits assigned to the Codeberg users, email addresses have to be verified.

this is not obviously not possible for users.noreply.github.com blackhole addresses.

We can set them to "verified" in the database manually, else they might be removed after 3 hours from the database - at least verification mails suggest that.

Same thing would be applicable to users.noreply.gitlab.com. Maybe automatically mark these domains as verified without having to actually verify them via email?

Is this still a thing or did anyone manage to solve this by now?

it's stil a thing - I think we can create a patch for codeberg that fix this in a save maner ... keep in mind not to allow any noreply mail by default as this would open dore to inpersonate people

idea: on mail adding check if it's no replay and if so check if it's gitlab or github ... then see if user did have the right account linked to the current account

(削除) https://docs.codeberg.org/git/configuring-git/ the <username>@noreply.codeberg.org address exists, however it doesn't work as expected for ssh signing. More of an upstream issue with gitea: https://github.com/go-gitea/gitea/issues/21692. (削除ここまで) I'm stupid, just use <username>@noreply.codeberg.org, it works.

It does work for SSH signature; it was implemented in Forgejo, forgejo/forgejo#1754. Gitea's issues are unrelated. If it does not work, please open a new issue on this issue tracker as it's unrelated to this issue.

You're right, it seems like for some reason git wasn't signing the first commit of my test repo (some edge case of using commit-tree without -S, TIL that [commit] gpgsign = true doesn't apply to commit-tree). Sorry for the confusion, it was my fault when testing.

Any updates on a issue?