-
Notifications
You must be signed in to change notification settings - Fork 250
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
The infamous CLA check is back #589
Comments
Looking at recent pull requests, I see no CLA checks anymore, so I think this is now properly disabled. I'll close this, we can reopen when this turns out to be false. |
A message has to be given in all PR with this wrong check then. |
I'd rather just delete the comments, let me do that. |
Seems there was just one CLA comment left, I deleted it. I also deleted @ederag's followup comments since they referred already deleted CLA comments, which probably only adds confusion. |
Ah, I was looking at the CLA assistant comments, but there are indeed still (or again) pending checks. I see this is only the case on some PRs and not new ones, so that probably means that the checks are properly disabled now, but the existing ones still linger. Not sure if they can be removed, maybe @ederag can. As for deleting comments, sorry for that. It seemed better to delete the CLA comments, and with that also your comment since it would otherwise not make sense. When I found no further CLA comments, I thought you were being overzealous in adding comments everywhere, but it seems I just missed the pending check. In any case, I reposted some comments, and posted one additional one, so I think all pending checks have not been covered and this can be closed again. Agreed? |
I suppose this can be closed now. |
@elbenfreund, it's back
It's most probably a mistake, as you well know this code is pure GPL,
and can never be re-licensed otherwise.
Please remove it, that scares contributors off,
and increases the risk of someone else putting a CLA on this by mistake.
The text was updated successfully, but these errors were encountered: