EasyCLA Troubleshooting

The following sections help you troubleshoot common problems that you might encounter when using the EasyCLA tool.

• GitHub pull request is not passing

• (GitHub) Unable to contribute to EasyCLA-enforced repositories

• (Gerrit) Unable to contribute to EasyCLA-enforced repositories

• (GitHub) Individual Contributor's EasyCLA status is not updated

• (Gerrit) Individual Contributor's EasyCLA status is not updated

• (GitHub) Corporate Contributor's EasyCLA status is not updated after being added to the approved list

• (Gerrit) Corporate Contributor's EasyCLA status is not updated after being added to the approved list

• EasyCLA status displays "Expected"​ in the "Checks" section of the Pull Request

• EasyCLA status does not change to "CLA SIGNED" for multiple open pull requests after signing ICLA and/or CCLA

• I cannot use EasyCLA for my Linux Foundation-hosted project

• My company is not displayed in the list when I am trying to contribute code under a corporate CLA (CCLA)

• I cannot view my individual CLA (ICLA) after I sign it

• A "Sanctions Screening" message blocks my organization

• EasyCLA is Disabled for a GitHub repository

GitHub pull request is not passing

Problem:

I have an agreement on file, but EasyCLA does not authorize me and displays UNKNOWN COMMIT AUTHOR.

Solution:

• Ensure that your commits are linked to your GitHub account. If your commits are not linked to any GitHub user, GitHub can display the grey Octocat logo beside the commits, and EasyCLA can show UNKNOWN COMMIT AUTHOR.

• If your commits are linked to your GitHub account and the pull request still does not pass, the EasyCLA comment badge may show SIGNED AGREEMENT MISSING. In the Checks section, the failing check can appear as Missing CLA Authorization. Open the pull request, type /easycla in the comment box, and click Comment as shown below. This runs the EasyCLA bot again.

Pull Request Commenting

(GitHub) Unable to contribute to EasyCLA-enforced repositories

Problem:

Contributors' commits are linked to their GitHub accounts, however, they are still facing issues contributing to EasyCLA-enforced repositories.

Solution:

• If your CLA Manager approved your Contributor’s Email or Email Address Domain, ensure that the same email is verified in your GitHub account settings and made public on the GitHub profile used for the contribution.

• If your CLA Manager approved your GitHub Username, ensure that you are contributing from that exact GitHub account.

• If your CLA Manager approved your GitHub Organization, ensure that you have made that membership public.

(Gerrit) Unable to contribute to EasyCLA-enforced repositories

Problem:

Contributor's commits are linked to Gerrit account, however, they are still having trouble contributing to EasyCLA-enforced repositories.

Solution:

Ensure that the Gerrit email address used for the contribution is added to the approved list under Contributor’s Email, or is covered by the approved Email Address Domain, and log in to the Gerrit instance using that same email address.

(GitHub) Individual Contributor's EasyCLA status is not updated

Problem:

After a Contributor has signed an ICLA, EasyCLA status is not updated on the contributor console.

Solution:

It may take a few moments for the status of the EasyCLA checks to update. Please wait a few moments and then refresh the page. **** If the EasyCLA status is still not updated, open the pull request, and comment /easycla in the comment section as shown below. This comment runs the bot again.

Comment /easycla in the Pull Request

(Gerrit) Individual Contributor's EasyCLA status is not updated

Problem:

After a Contributor has signed an ICLA, EasyCLA status on Git command line still displays "No contributor agreement" when the contributor pushes the code change.

Solution:

Navigate to the Gerrit window, sign out, sign in again, and then push the code.

(GitHub) Corporate Contributor's EasyCLA status is not updated

Problem:

For a CCLA, after a Contributor has been added to the approved list for the first time, the EasyCLA status may still display MISSING COMPANY AFFILIATION.

Solution:

After being added to the approved list under their company's signed CCLA, the Contributor must acknowledge their association with the company. This is a one-time action and, after completion, it will not be required for future contributions to that project.

Although it is uncommon, some projects may require a Contributor under a CCLA to additionally sign an ICLA. If this is required, then after completing the company acknowledgement, the Contributor will be guided to sign the project's ICLA.

(Gerrit) Corporate Contributor's EasyCLA status is not updated

Problem:

For a CCLA, after a contributor has been added to the approved list for the first time, the CLA status on the Git command line still displays No contributor agreement when you push the code change.

Solution:

Navigate to the Gerrit window, sign out, sign in again, and then push the code.

EasyCLA status displays "Expected"​ in the "Checks" section of the Pull Request

Problem:

In the “Checks” section of the pull request, EasyCLA status is showing as “Expected”.

Solution:

Open the pull request, and comment /easycla in the comment section as shown in the image below. This comment runs the bot again.

Comment /easycla in the Pull Request

EasyCLA status does not change to "CLA SIGNED" for multiple open pull requests after signing ICLA and/or CCLA

Problem:

After signing an ICLA or verifying under a CCLA, the status does not change to CLA SIGNED for multiple open pull requests.

Solution:

Open one pull request, and comment /easycla in the comment section as shown in the image below. This comment runs the bot again.

Comment /easycla in the Pull Request

My company is not displayed in the list when I am trying to contribute code under a corporate CLA (CCLA)

Problem:

When I am trying to contribute code under a CCLA, my company is not displayed in the list.

Solution:

You must create a record for your company as described here.

I cannot view my individual CLA (ICLA) after I sign it

Problem:

I have signed an ICLA; however, I cannot view the signed ICLA.

Solution:

Open your email, that you have provided while signing the ICLA, to check the signed ICLA that is sent from The Linux Foundation.

A "Sanctions Screening" message blocks my organization

Problem:

When I select my company in the EasyCLA Contributor Console, a Sanctions Screening dialog appears, and I cannot complete the company acknowledgement (ECLA). Or, when signing our company's CCLA, the dialog shows Unable to Prepare CCLA with a message that the organization is flagged by sanctions screening.

Solution:

EasyCLA automatically screens organizations against government sanctions lists, and blocks the CCLA and ECLA workflows for flagged organizations. Individual CLAs (ICLA) are not affected.

• If you believe your organization is flagged in error, contact EasyCLA support via the chat widget in the console, or file a support ticket. The compliance team will review the screening result.

• After your organization is cleared, wait a few minutes, and then retry the blocked action. EasyCLA re-screens the organization automatically — no other action is needed.