Hi, when you push a change you have to use the same 'committer' field of the account used for authenticating on Gerrit. This will report 'who' push the patch
Nevertheless you can push the patch with the 'author' field reporting another user. This reports 'who' wrote the code and can be different from 'committer'. Pay attention that check patch requires the commit message to have the same author to sign-off the patch. It's also good practice to have the committee to sign it off too. Antonio On Tue, Jan 14, 2025, 20:06 <conor.pax...@microchip.com> wrote: > Hi There, > > I am facing a bit of a problem. I initially proposed a series of commits > to provide support for Microchip debug probes. > Another member of our team is now assigned to work on getting the support > upstream, however I am unable to push > the rebased patch set to master. I get the following error: > > "remote: ERROR: commit e89a86d: email address emma.davenp...@microchip.com > is not registered in your account, and you lack 'forge committer' > permission. > remote: The following addresses are currently registered: > remote: conor.pax...@microchip.com" > > What would be the best way to proceed? As I see it, If the member of our > team pushes to review/master, it will duplicate > the patch set. > Would it be best for me to abandon the patches that I have pushed? If so, > what would happen with the review comments that have been > left on it? The commits will all have the same "Change-ID" that was > injected into each commit by the git hook. > > Any help would be greatly appreciated. > Kind Regards, > Conor >
