Hi Junio & Aleen, On Fri, 19 Nov 2021, Junio C Hamano wrote: > Aleen 徐沛文 <pwxu@xxxxxxxxxxx> writes: > > >> Yes. > >> > >> As the URL you were referred to explains, the sign-off procedure is > >> to keep track of provenance of the code, which is a more "legal" > >> formal requirement than just "I use this pseudonym everywhere". > >> When a big company comes to us, claiming that "this code is our > >> intellectual property stolen from us" and pointing at code added by > >> a patch from you, we do not want to see us in the position to have > >> to say "eh, somebody who uses psuedonym X signed DCO, but we do not > >> even know their real name". > > > > I know it, and as I said before that gitgitgadget need PR creators to > > sign off user name of GitHub account, according to the DCO check. I can > > confirmed that "Aleen" and "Aleen 徐沛文" are both the real name of mine, > > the committer. I can use the account aleen42@xxxxxxxxxx to confirm this. > > Can somebody from GGG land help this user? I _think_ the easiest > workaround (other than not using GGG and sending e-mail in the old > fashioned way) is to commit and sign-off under the real name, and > push under whatever GitHub username to throw a GGG pull request, > which GGG should be able to take, as I have seen users forward other > authors commits just fine. GitGitGadget looks at the author information, so you need to ensure that the "Author:" line in the output of `git log` shows the desired name. If it does not, you need to configure `user.name` (and user.email)` as desired, and then re-commit with `git commit --amend --reset-author`, then force-push. Ciao, Johannes
