If you are having issues with EasyCLA, go to The Linux Foundation Support Center, and file a ticket.
The following sections help you troubleshoot common problems that you might encounter when using the EasyCLA tool.
I have an agreement on file, but EasyCLA does not authorize me and displays "Missing ID on Commit".
If your commits are linked to your GitHub account, and yet the GitHub pull request is not passing the EasyCLA check, then open the pull request, type/easycla in the comment box, click Comment as shown below. This runs the EasyCLA bot again, and the GitHub pull request is passed.
Contributors' commits are linked to their GitHub accounts, however, they are still facing issues contributing to EasyCLA-enforced repositories.
If your CLA Manager has approved your company email address or email domain, ensure that your company email is verified in your GitHub account settings and make sure your GitHub email address is public.
Or
If your CLA Manager has approved your GitHub Organization, ensure that you have made that membership public.
Contributor's commits are linked to Gerrit account, however, they are still having trouble contributing to EasyCLA-enforced repositories.
Ensure that your Gerrit email address is added to the approved list, and you must log in to the Gerrit instance of your project using the same email address that is added to the approved list.
After a Contributor has signed an ICLA, EasyCLA status is not updated on the contributor console.
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. If the status still does not change, open a support ticket.
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.
For a CCLA, after a Contributor has been added to the approved list for the first time, the CLA status still displays Not Covered.
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.
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.
Navigate to the Gerrit window, sign out, sign in again, and then push the code.
In the “Checks” section of the pull request, EasyCLA status is showing as “Expected”.
Open the pull request, and comment /easycla in the comment section as shown in the image below. This comment runs the bot again. If the status still does not change, open a support ticket.
After signing an ICLA or verifying under a CCLA, the status does not change to “Authorized” for multiple open pull requests.
Open one pull request, and comment /easycla in the comment section as shown in the image below. This comment runs the bot again. If the status still does not change, open a support ticket.
After hosting my project on The Linux Foundation, I can not use EasyCLA for my project.
Open https://jira.linuxfoundation.org/plugins/servlet/theme/portal/4/create/143, submit the form describing your requirements, and import your existing CLAs.
When I am trying to contribute code under a CCLA, my company is not displayed in the list.
You must create a record for your company as described here.
I have signed an ICLA; however, I cannot view the signed ICLA.
Open your email, that you have provided while signing the ICLA, to check the signed ICLA that is sent from The Linux Foundation. If you have not received the email, you can open a support ticket to have it resent.
\
Ensure that your commits are linked to your GitHub account. If your commits are not linked to any GitHub user, GitHub will display the grey Octocat logo beside the commits.
Navigate to the Gerrit window, sign out, sign in again, and then push the code.
EasyCLA was previously enabled for a GitHub repository, but someone other than the project manager has subsequently disabled it.
GitHub is set up to permit administrators and organization owners to have maximum flexibility, which includes disabling installed applications, such as EasyCLA. To avoid this, you must enable branch protection by after the GitHub organization is added to a project.
You can also add the branch protection rule manually, as described below:
1. As the GitHub organization owner or administrator, go to the GitHub repository that you want EasyCLA to monitor.
2. Click Settings from the top menu.
3. Settings appear with Options in the left pane.
4. Click Branches under Options.
5. Select master for the Default branch. Click Edit or Add rule for Branch protection rules of your organization.
6. Select the following check boxes under Rule settings, and click Create:
Require status checks to pass before merging
Require branches to be up to date before merging
Include administrators
