Summary
EasyCLA is not sending the ICLA email with a CLA status of UNKNOWN COMMIT AUTHOR. I performed 5 signatures, none of them dispatched the email with the UNKNOWN COMMIT AUTHOR
It does work as expected with the SIGNED AGREEMENT MISSING information. I performed 1 signature with SIGNED AGREEMENT MISSING message, immediately received the email.
It seems the signed document is not getting uploaded to S3 when UNKNOWN COMMIT AUTHOR is present.
Background
When the individual contributors signed the CLA, even with an UNKNOWN COMMIT AUTHOR message, EasyCLA provides the SIGNED AGREEMENT MISSING link. When user select that option and sign the ICLA. EasyCLA does not dispatch the email.
It works without issues when only SIGNED AGREEMENT MISSING
Expected behavior
Regardless of the message, EasyCLA should always dispatch the ICLA email using Mandrill. Example:
Summary
EasyCLA is not sending the ICLA email with a CLA status of UNKNOWN COMMIT AUTHOR. I performed 5 signatures, none of them dispatched the email with the UNKNOWN COMMIT AUTHOR
It does work as expected with the SIGNED AGREEMENT MISSING information. I performed 1 signature with SIGNED AGREEMENT MISSING message, immediately received the email.
It seems the signed document is not getting uploaded to S3 when UNKNOWN COMMIT AUTHOR is present.
Background
When the individual contributors signed the CLA, even with an UNKNOWN COMMIT AUTHOR message, EasyCLA provides the SIGNED AGREEMENT MISSING link. When user select that option and sign the ICLA. EasyCLA does not dispatch the email.
It works without issues when only SIGNED AGREEMENT MISSING
Expected behavior
Regardless of the message, EasyCLA should always dispatch the ICLA email using Mandrill. Example: