-
-
Notifications
You must be signed in to change notification settings - Fork 94
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Feature] Add option to require full name when signing CLA #58
Comments
Hi @Holzhaus, thank you very much for reaching out to us. One thing to note is that this bot already stores the contributor's GitHub account id which is immutable and so won't be altered even if the contributor changes his/her GitHub name. This CLA bot stores the below information when the contributor signs the CLA "signedContributors": [
{
"name": "ibakshay",
"id": 33329946,
"comment_id": 712807508,
"created_at": "2020-10-20T12:16:24Z",
"repoId": 282192792,
"pullRequestNo": 155
} |
I'm not a lawyer, but there were concerns that a GitHub username might turn out to be insufficient in case of lawsuit. Do the lawyers at SAP think the username suffices? If so, this might be unnecessary. |
As a first step, it would be nice if signature contained the full name from the github profile, i.e. read the "name" value from |
Hi, we would also appreciate this feature, as adding the option to specify an affiliation. Anything we can do to accelerate the development? Is there already a PR? |
I'm not a lawyer, but our team was discussing if just recording the GitHub user name is enough. People might delete their accounts or their PR and we're unsure this could cause problems.
How about adding an options to require the actual name when signing, e. g.:
It could then parse the name and add it to the JSON file. If the name is not present, doesn't consist of at least two words or contains invalid characters (e. g.
*<>^~¿
;÷|` etc.), the bot either ignores the message or posts an error message.The text was updated successfully, but these errors were encountered: