Contributing to OpenParachute

Thanks for contributing! This page covers the org-wide basics; individual repos may add their own conventions in a repo-level CONTRIBUTING.md or CLAUDE.md.

Contributor License Agreement (CLA)

All contributions to OpenParachute repositories require a signed Contributor License Agreement. When you open your first pull request, the CLA bot will ask you to sign by posting this exact comment on the PR:

I have read the CLA Document and I hereby sign the CLA

You sign once — your signature is recorded org-wide in ParachuteComputer/cla-signatures and covers all current and future contributions to any OpenParachute repository.

Why a CLA? OpenParachutePBC needs licensing flexibility to sustain the project (e.g. offering commercial licensing alongside AGPL). The CLA is a license, not a copyright assignment — you keep ownership of your work — and §9 (the OpenParachute Pledge) commits that everything you contribute stays available under an OSI-approved open-source license.

If the bot's check is stuck after you've signed, comment recheck on the PR.

Pull request flow

1. Fork the repo (or branch, if you have write access) and make your change.
2. Open a PR against main. Keep PRs focused — one coherent change per PR.
3. Run the repo's test and typecheck scripts before opening the PR (usually bun test and bun run typecheck — check the repo's package.json).
4. All repos use PR-required branch protection; a maintainer reviews and merges.

Questions

Open an issue on the relevant repo, or see parachute.computer for project documentation.