EasyCLA not able to fetch the commit author information from GitHub bots

[jarias-lfx]

Summary

Support has received several reports from EasyCLA not longer been able to fetch the commit author information from GitHub bots.

Background

EasyCLA fetches the author information from the commit and validates the author agains EasyCLA database to conform the presence of an ECLA or ICLA. Currently this is failing for all GitHub bots and EasyCLA reports Missing ID on Commit

Affected PRs:

• Bump github.com/aws/aws-sdk-go-v2/config from 1.27.33 to 1.27.34 in the gomod group cloudfoundry/korifi#3478
• chore(deps): update dependency com.puppycrawl.tools:checkstyle to v10.18.1 cloudfoundry/app-autoscaler-release#3210
• Iteration Release v12.40.0 finos/legend-studio#3529
• Prepare New Iteration Release finos/legend-studio#3530
• Bump Google.Protobuf from 3.27.1 to 3.28.1 open-telemetry/opentelemetry-dotnet-instrumentation#3642
• Bump confluentinc/cp-kafka from 7.7.0 to 7.7.1 in /test/IntegrationTests/docker open-telemetry/opentelemetry-dotnet-instrumentation#3645
• build(deps): bump versions.tomcatVersion from 9.0.94 to 9.0.95 cloudfoundry/uaa#3050
• build(deps): bump versions.tomcatCargoVersion from 9.0.94 to 9.0.95 cloudfoundry/uaa#3051
• chore(deps-dev): bump the dependencies group across 1 directory with 4 updates webpack/webpack#18770
• Bump pypa/cibuildwheel from 2.21.0 to 2.21.1 AcademySoftwareFoundation/openexr#1824

Expected behavior

EasyCLA should be able to fetch the author information from GitHub bots.

Workaround

Please contact the project owners or maintainers to force merge the PR without EasyCLA for the GitHub bots if urgent, while EasyCLA investigates the issue.

[jarias-lfx]

It seems to be working again.

Note for AlanGreene: /easycla comment is not working in tektoncd, we have requested the owners to check if there is configuration that is blocking comment actions in the organization. Maybe closing/re-open the PR work this time.

[AlanGreene]

Thanks @jarias-lfx. I'll work with the other maintainers to see if we can unblock the /easycla command as there are quite a few PRs affected and I'd rather not have them all re-trigger all of their CI jobs.

[afrittoli]

I think the problem with the /easycla command might be that EasyCLA is asking for new permissions that we have not granted yet:

What does EasyCLA need read/write administration of the GitHub org for?
We use peribolos to maintain some of org settings and I would like to avoid having conflicting changes from EasyCLA.

@vdemeester FYI

[vdemeester]

@afrittoli ah good point. I think I missed those "new permissions" request then 😓

[AlanGreene]

What does EasyCLA need read/write administration of the GitHub org for?

@jarias-lfx is that something you can answer?

[nickmango]

@mlehotskylf will need your help in checking the easycla bot admin config settings

[mlehotskylf]

@afrittoli @vdemeester These are the original permissions that must be accepted when the EasyCLA GitHub app is first installed. Without them, EasyCLA may not function as intended. It’s important to note that EasyCLA isn’t requesting administrative write access to gain full control over your repository. Instead, it needs this level of permission because core features—such as setting up webhooks or enforcing mandatory checks—fall under GitHub’s “Administration” category. Since these capabilities are integral to EasyCLA’s operation, the app must request write access to administration.

For reference, here are all the permissions EasyCLA is requesting:

CC: @jarias-lfx

[mlehotskylf]

Closing this ticket as resolved.
@afrittoli @vdemeester please feel free to open new ticket if you have any more questions.
Thank you!