PRO-1312: Document the automated CLA process - #1725
Open
qunabu wants to merge 3 commits into
Open
Conversation
The contributing guide asked contributors to sign a Contributor License Agreement via a Google Form, without explaining why the CLA exists, what it covers, where signature records live, or how a signature is verified before a pull request is merged. - docs/guide/contributing.md gains a Contributor License Agreement section: why it is required, that one signature covers both HyperFormula and Handsontable, the four steps a contributor sees, that cla/signed is a required check, where records are stored, and a note telling reviewers the check is the verification. - Replaces the retired Google Form link with the signing page in the contributing guide, the PR template, README.md, and docs/index.md. The signature is recorded per GitHub account rather than per repository, so signing from either project clears the other.
✅ Deploy Preview for hyperformula-dev-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
12 tasks
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
hyperformula-docs | 96bf2f2 | Commit Preview URL Branch Preview URL |
Aug 11 2026, 09:31 AM |
Performance comparison of head (96bf2f2) vs base (61ead73) |
The gate is now served on its own hostname in the Handsontable Cloudflare account, so the docs no longer reference a sandbox workers.dev URL.
qunabu
marked this pull request as ready for review
August 11, 2026 09:28
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## develop #1725 +/- ##
========================================
Coverage 97.31% 97.31%
========================================
Files 195 195
Lines 15719 15719
Branches 3455 3455
========================================
Hits 15297 15297
Misses 414 414
Partials 8 8 🚀 New features to boost your workflow:
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Context
Documents the Contributor License Agreement process, which until now pointed contributors at a Google Form with no explanation attached.
The contributing guide asked contributors to sign a CLA, but nothing explained why it is required, what it covers, where signature records live, or how a signature is verified before a pull request is merged. PRO-1312 asks for that explanation in one place, for HyperFormula and Handsontable alike.
Two facts in particular were not written down anywhere a contributor would look:
cla/signedstatus check on every pull request, so an unsigned PR cannot be merged and no reviewer has to check anything by hand.What changed:
docs/guide/contributing.md— newContributor License Agreementsection covering the reasoning, the cross-project scope, the four steps a contributor sees, the required check, where records are stored, and a note for reviewers. Step 1 of "How to get started" now links to it..github/pull_request_template.md,README.md,docs/index.md— the retired Google Form link is replaced by the signing page.The signing page and the full process description are served by the CLA gate worker, which lives in a separate repository. The Handsontable counterpart to this PR is linked below; both repositories deliberately carry the same wording.
How did you test your changes?
Documentation-only change; no library code is touched.
docs/.vuepress/dist/, which is rebuilt):#contributor-license-agreementmatches the new heading, so step 1 of "How to get started" resolves both on GitHub and on the rendered docs site.Types of changes
Related issues:
Checklist:
cla/signedcheck on this PR confirms it.(The OpenDocument/Excel/Sheets and changelog items do not apply to a documentation-only change.)
Before merging
Two operational steps must land first, or contributors get a worse experience than today:
cla/signedas a required check ondevelop, so it actually blocks a merge. The App is now installed here and the check has been verified green on this PR.ClickUp task: https://app.clickup.com/t/9015210959/PRO-1312
Note
Low Risk
Documentation-only changes with no runtime or library code impact.
Overview
Replaces the retired Google Form CLA link with cla.handsontable.com/sign in the PR template,
README.md, anddocs/index.md, and clarifies that one signature covers HyperFormula and Handsontable via thecla/signedcheck.Adds a Contributor License Agreement section to
docs/guide/contributing.md(why the CLA exists, cross-repo scope, PR flow with the GitHub App, required check, EU D1 storage, reviewer guidance). Step 1 of “How to get started” now links to that section instead of the old form URL.Reviewed by Cursor Bugbot for commit 25c96da. Bugbot is set up for automated code reviews on this repo. Configure here.