contributor check can fail on master after CI pass on PR

[Sekkmer]

if you push commits with a different email than your default settings in GitHub the contributor check may get broken on squash merge as it will always use the default one

[Jomshir98]

I'm aware of that, but I'm not sure if there is way we can detect it reasonably (if we want to keep squash merging).
The issue is that when squash merging author can choose different email altogether over the commit emails...
Possible solutions I see are:

• Leave as-is - new contributors are not unlikely to encounter this, but we can fix it quickly as we know about it - with further PRs they just need to use already working email and it can't fail
• Try to find out possible values for this commit from GH and check against those
• Ignore checking email, only check part of Author of commit. (for example strip away email using regex before comparing)
• Do not check as part of PR, but have post-merge CI commit to master adding the value based on last merge

[Sekkmer]

one possible option is to only allow lead developers to merge PRs, as in that case co-author will be filled correctly