# 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-pull-request-is-not-passing) * [(GitHub) Unable to contribute to EasyCLA-enforced repositories](#github-unable-to-contribute-to-easycla-enforced-repositories) * [(Gerrit) Unable to contribute to EasyCLA-enforced repositories](#gerrit-unable-to-contribute-to-easycla-enforced-repositories) * [(GitHub) Individual Contributor's EasyCLA status is not updated](#github-individual-contributors-easycla-status-is-not-updated) * [(Gerrit) Individual Contributor's EasyCLA status is not updated](#gerrit-individual-contributors-easycla-status-is-not-updated) * [(GitHub) Corporate Contributor's EasyCLA status is not updated after being added to the approved list](#github-corporate-contributors-easycla-status-is-not-updated) * [(Gerrit) Corporate Contributor's EasyCLA status is not updated after being added to the approved list](#gerrit-corporate-contributors-easycla-status-is-not-updated) * [EasyCLA status displays "Expected"​ in the "Checks" section of the Pull Request](#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](#easycla-status-does-not-change-to-cla-signed-for-multiple-open-pull-requests-after-signing-icla-and) * [I cannot use EasyCLA for my Linux Foundation-hosted project](#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)](#my-company-is-not-displayed-in-the-list-when-i-am-trying-to-contribute-code-under-a-corporate-cla-cc) * [I cannot view my individual CLA (ICLA) after I sign it](#i-cannot-view-my-individual-cla-icla-after-i-sign-it) * [EasyCLA is Disabled for a GitHub repository](https://docs.linuxfoundation.org/lfx/easycla/v2-current/getting-started/easycla-troubleshooting/easycla-disabled) ## 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](https://docs.github.com/en/github/committing-changes-to-your-project/why-are-my-commits-linked-to-the-wrong-user#commits-are-not-linked-to-any-user). If your commits are not linked to any GitHub user, GitHub can display the *grey Octocat logo* ![](https://3411187760-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M2DCN9UgoRgMEkgnLyP-887967055%2Fuploads%2Fgit-blob-d5746f0e90bab79a53ff7db27c9cd2a9c41edc52%2Fgrey%20colored%20octobat.png?alt=media\&token=b6a1e52c-1211-4fe4-9ff1-2f1d7718f087) 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](https://3411187760-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M2DCN9UgoRgMEkgnLyP-887967055%2Fuploads%2Fgit-blob-25736a915a505d0fedf8c4a8b98a1b4c2021ef5c%2Fpull%20request%20commenting.png?alt=media\&token=517ce3dd-886a-4764-9331-92667cdcef1e) ## (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](https://docs.github.com/en/github/getting-started-with-github/verifying-your-email-address) 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](https://docs.github.com/en/github/setting-up-and-managing-your-github-user-account/publicizing-or-hiding-organization-membership). ## (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](https://3411187760-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M2DCN9UgoRgMEkgnLyP-887967055%2Fuploads%2Fgit-blob-25736a915a505d0fedf8c4a8b98a1b4c2021ef5c%2Fpull%20request%20commenting.png?alt=media\&token=517ce3dd-886a-4764-9331-92667cdcef1e) ## (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.\ ![](https://3411187760-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M2DCN9UgoRgMEkgnLyP-887967055%2Fuploads%2Fgit-blob-cb797d1120481f83d8cc08369fd34e5110d0cd75%2Fsignout%20gerrit.png?alt=media\&token=b6534b06-adff-4d97-8adb-422c4d474d13) ## (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](https://docs.linuxfoundation.org/lfx/easycla/contributors/corporate-contributor#acknowledge-company-contribution). 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](https://docs.linuxfoundation.org/lfx/easycla/contributors/corporate-contributor#if-you-are-asked-to-sign-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. ![](https://3411187760-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M2DCN9UgoRgMEkgnLyP-887967055%2Fuploads%2Fgit-blob-cb797d1120481f83d8cc08369fd34e5110d0cd75%2Fsignout%20gerrit.png?alt=media\&token=b6534b06-adff-4d97-8adb-422c4d474d13) ## 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](https://3411187760-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M2DCN9UgoRgMEkgnLyP-887967055%2Fuploads%2Fgit-blob-25736a915a505d0fedf8c4a8b98a1b4c2021ef5c%2Fpull%20request%20commenting.png?alt=media\&token=517ce3dd-886a-4764-9331-92667cdcef1e) ## 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](https://3411187760-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M2DCN9UgoRgMEkgnLyP-887967055%2Fuploads%2Fgit-blob-25736a915a505d0fedf8c4a8b98a1b4c2021ef5c%2Fpull%20request%20commenting.png?alt=media\&token=517ce3dd-886a-4764-9331-92667cdcef1e) ## 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](https://docs.linuxfoundation.org/lfx/easycla/contributors/corporate-contributor#if-your-company-is-not-in-the-list). ## 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.