Thank you for helping improve TypeWhisper. Use the repository that owns the feature or integration you want to change, and follow its build and test instructions. Keep pull requests focused and describe the behavior changed and the checks you ran.
TypeWhisper offers its software under open-source licenses and, where applicable, separate commercial terms. Contributions need to support both forms of distribution.
Our Contributor License Agreement lets you retain ownership of your work while granting TypeWhisper the rights to use, modify, distribute, and sublicense it, including under commercial terms. Read the complete agreement before accepting it.
Read and accept the agreement at app.typewhisper.com/cla. Signing uses your GitHub account and does not require a paid TypeWhisper license. Signing in or opening a pull request does not itself record acceptance.
Each contributor accepts the current agreement once for all covered TypeWhisper projects. A changed agreement version requires fresh acceptance. Every human contributor whose work is included in a pull request must be covered; the person opening the pull request cannot accept for everyone else. A DCO sign-off or cryptographic commit signature does not replace CLA acceptance.
You can open a pull request before accepting. The TypeWhisper CLA check links
to the signing portal and identifies contributors who still need to accept or
confirm the pending pull request. It runs again after acceptance. Participating
public repositories require a successful check for the current agreement before
merging into the default branch, alongside their existing review and CI rules.
Acceptance covers future contributions. To cover a pull request that was already open when you accepted, explicitly select and confirm it in the signing portal. Previously merged contributions require separate explicit confirmation.
Bug reports, questions, and discussions do not require signing. Forks of external projects follow their upstream contribution rules, rather than this CLA.
Check whether your employer or client owns rights to your contribution. If they do, obtain their authorization or contact licensing@typewhisper.com to arrange a corporate agreement before contributing.
Identify third-party material and preserve its source, license, and notices. The CLA does not relicense dependencies or other people's code. The repository's license describes the rights recipients receive; the CLA separately describes the rights contributors grant TypeWhisper.
- Explain the problem and resulting behavior, and reference a relevant issue.
- Include the verification commands and results appropriate to your change.
- Keep credentials, private customer data, and confidential company information out of code, fixtures, screenshots, and discussion.
- Use the project's existing patterns and keep unrelated changes separate.
Changes to the signing process and previous contributions are tracked by the maintainers separately. No contributor will be marked as having signed merely because they previously submitted or merged a pull request.