Why Handsoncode asks for a CLA, what it covers, and how the check on your pull request works.
Sign the CLAHandsoncode publishes the code it merges — in open-source releases and in commercial products. To do that, it needs the right to use, relicense, and distribute every contribution. The CLA is the record of that permission. Without it, the ownership of a merged pull request is unclear, which blocks releases and creates attribution problems years later.
You keep the copyright to your work. The CLA grants Handsoncode a licence to it; it does not transfer ownership.
One signature, all projects. The agreement is recorded against your GitHub account, not against a repository, so it applies to every Handsoncode open-source project:
If you have already signed for one of them, you are done — the check on a pull request in the other passes automatically.
cla/signed status check on your commit.Members of the handsontable GitHub organization and known bots are exempt — their contributions are covered by other agreements.
There is nothing to verify by hand. The cla/signed status check is a required check on the default branch of every covered repository, so an unsigned pull request cannot be merged — the merge button stays blocked. Do not merge a pull request whose CLA check is red, and do not attempt to work around it.
| Item | Detail |
|---|---|
| Current CLA version | 1.0 |
| Agreement text | https://cla.handsontable.com/sign |
| Signature records | Cloudflare D1, EU West region |
| Stored per signature | GitHub login, name, email, optional company, CLA version, timestamp, originating pull request |
| Retention | Kept indefinitely as a legal record |
For anything about the agreement, a correction to your record, or an erasure request, email support@handsontable.com.