| Summary: | eclipsefdn/eca bot is failing a check on my Github account | ||
|---|---|---|---|
| Product: | Community | Reporter: | Tim Ellison <t.p.ellison> |
| Component: | My Account | Assignee: | phoenix.ui <phoenix.ui-inbox> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | major | ||
| Priority: | P3 | CC: | chris.guindon, eric.poirier, martin.lowe, webdev, webmaster |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
|
Description
Tim Ellison
FYI I have committed to other repos successfully, so it may be specific to github.com/adoptium/temurin-build Did you make this change via the Github web-UI or via cli tools? -M. > Did you make this change via the Github web-UI or via cli tools?
Github web-UI
Eric, Martin, Can you both take a look at this? I am not sure if the error is on the drupal site (accounts.eclipse.org) or the ECA validation service. However, Tim has a valid ECA on file so this check should pass. He's using his github no.reply email for this PR: https://api.github.com/repos/adoptium/temurin-build/pulls/2623/commits We can trace back this GitHub no-reply email to an Eclipse account: https://api.eclipse.org/github/profile/tellison Tim, feel free to tell the project that they can merge your PR while we work on a fix for this They can validate your ECA status by clicking on your name here: https://accounts.eclipse.org/legal/eca/validation/67859 We recently made an update to the ECA validation service and I think we introduced a regression when a contribution is made with a @users.noreply.github.com email. Thanks, I will proceed to merge this contribution while the fix is being worked. Fix is up for review in the APIs GH repo: https://github.com/EclipseFdn/git-eca-rest-api/pull/60 From what I can tell Chris is dead on the money, this was a regression around no reply. I added the gh no reply and some tests so we can make sure we can catch this in the future! Let me know when you are ready, and I am happy to recheck my PRs with the patched bot. (In reply to Tim Ellison from comment #8) > Let me know when you are ready, and I am happy to recheck my PRs with the > patched bot. Looks like the fix is live! We had a snappy review so I was able to push it up. From my tests it looks good, so let me know if it works for you as well! Check now works for me - thanks. (In reply to Tim Ellison from comment #10) > Check now works for me - thanks. Thanks Tim! Its always appreciated, thanks for submitting the bug and throwing in an extra test case for us to boot |