Using a commit email different from Eclipse registration email works for commits... not for merge requests!

Summary

Basically, it is possible to fork a project, clone it, then commit (locally) with any email address (provided you use the Eclipse credentials to push).

If doing so, don't even think of having it merged in the original project (rejected with error message "Could not find an Eclipse user with mail 'your-email' for author of commit" - if "your-email" is different from the one used for Eclipse registration).

Not sure it is a "normal" behaviour (I don't think so).

Then I tried something else:

• Registering "my-email" as commit email in the Gitlab interface
• Trying the merge again.

Same error: so one can't merge a fork that was updated... using his declared commit email. I am wondering what the "commit email" is intended for, then (?)

What is the expected correct behavior?

Anything that could be properly pushed using my Eclipse credentials should be allowed to be merged. And it is rejected because of alleged unauthorized user ("Author must have an Eclipse Account").

Relevant logs and/or screenshots

(note: I anonymized the email in the sample below)

remote: Commit: a83c2e82dc5700a321e1d7d4ceb3c995854338be        X
remote: 
remote:     Reviewing commit: a83c2e82dc5700a321e1d7d4ceb3c995854338be
remote:     Authored by: gibello <gibello@xxx.org>
remote:     Could not find an Eclipse user with mail 'gibello@xxx.org' for author of commit a83c2e82dc5700a321e1d7d4ceb3c995854338be
remote: 
remote: Errors:
remote: Author must have an Eclipse Account
remote: Any warnings or errors noted above may indicate compliance issues with committer ECA requirements. More information may be found on https://www.eclipse.org/legal/ECA.php

Priority

• Urgent
• High
• Medium
• Low

Severity

• Blocker
• Major
• Normal
• Low

Impact

Blocked an approved merge for hours (we had to reinject the commits in a new fork).