Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Do I have to sign my own CLA? #309

Closed
LNFWebsite opened this issue Feb 21, 2018 · 1 comment
Closed

Do I have to sign my own CLA? #309

LNFWebsite opened this issue Feb 21, 2018 · 1 comment

Comments

@LNFWebsite
Copy link

This isn't a bug with CLA Assistant so much as it is a general question.

When submitting PRs to my own project (I make changes via commits to master and then merge them into the gh-pages branch), should I sign my own CLA?

I'm not savvy to the legalities of signing my own CLA but wanted to make sure that it is common practice before I do it...

Thanks!
@KharitonOff
Copy link
Contributor

this is not really a common practice, but it is how CLA Assistant is designed now. Maybe we'll get a contribution which addresses this issue... (see #197 )

@KharitonOff KharitonOff mentioned this issue Feb 11, 2019
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@KharitonOff @LNFWebsite