Closed Adityajaiswal03 closed 3 months ago
Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).
View this failed invocation of the CLA check for more information.
For the most up to date status, view the checks section at the bottom of the pull request.
Ah actually it looks like you haven't signed the CLA @Adityajaiswal03 , could you go ahead and do that for me?
Hi @BeksOmega , I have already signed the Contributor License Agreement (CLA), but it appears that it has not been processed yet. Could you please assist me with this issue?
Hello @Adityajaiswal03
Have you tried following the instructions in the check response?
Help! I've signed the CLA, but it's still showing me as unsigned.
Individual signers
- It's possible we don't have your GitHub username. Verify that your existing CLA data is accurate.
- You may not be using the email associated with your CLA in your Git commits. Check that the email set on your git commits matches the email associated with your CLA.
Corporate signers
- Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
- The email used to register you as an authorized contributor must be the same email used in your Git commits. Check your existing CLA data and verify that your email is set on your git commits.
- The email used to register you as an authorized contributor must also be attached to your GitHub account.
- You may have Keep my email address private enabled. Without a visible email address, the CLA cannot be checked. Uncheck it and re-create the offending commit, or have your CLA point of contact add your @users.noreply.github.com address to the CLA group.
@BeksOmega, I'm still encountering the issue, so I'm going to delete this PR and create a new one against the same branch.
solves #8290