-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Add contributor agreement for contributors #1833
Comments
I originally implemented the CLA using clahub but reverted when I Do you know if they have changed it to not require anything beyond |
I think those levels of permissions are part and parcel with those integrations, it seems. The way to protect ones private repos would be to set up an organization, which gives more granular access i.e. you can specifically disable all third party access until explicitly granted for each integration. |
It wasn't just that clahub required giving it permission to the Knockout repos. It also required everyone who used it to sign the CLA to give it full access to their GitHub accounts. That seems completely mad to me - I know I'd certainly not grant it such permissions - I don't think signing any CLA would be important enough to justify doing that. Maybe this has changed. |
@SteveSanderson Oh yes, I see. That is madness. I like the concept, but yes... madness. :) Will try to look into it and post back here. |
Incidentally, this came to mind because I went through a similar process when contributing a PR to Karma via karma-runner/karma#1513 |
Alternatives include https://cla-assistant.io/
Note clahub/clahub#111
The text was updated successfully, but these errors were encountered: