Merge queue support
Auto-passes checks on merge queue commits. Compliance is verified on the PR — queue entries are never blocked.
Install a GitHub App, upload your CLA in Markdown, and every pull request is checked automatically. Signatures are tracked by immutable GitHub ID and SHA-256 content hash. Self-hostable. MIT licensed.
Setup takes less time than writing the CLA itself.
Sign in as an org admin, install CLA Bot, and select which repositories to monitor.
Paste your agreement in Markdown. Every version is tracked by its SHA-256 hash.
Non-members get signing guidance. Checks update automatically after signature.
Merge queues, bot accounts, policy changes, manual re-checks — covered.
Auto-passes checks on merge queue commits. Compliance is verified on the PR — queue entries are never blocked.
Exempt CI bots, GitHub Apps, and specific users per org. Slug matching treats mybot and mybot[bot] as equivalent.
Update CLA text, change bypass lists, or toggle enforcement — all open PRs recheck automatically via async workflows.
PR authors, org members, and maintainers re-trigger CLA checks with a comment. Unauthorized users are blocked.
Signatures are cryptographically versioned and immutably stored. Both admins and contributors can download records.
No delete endpoints exist for signature data. Records are append-only at the database level.
Signatures cannot be deleted. Every record is preserved with timestamp, hash, and session evidence.
Each CLA version is identified by its SHA-256 hash. Text changes produce a new hash and trigger re-signing.
Signatures are keyed by GitHub user ID, not username. Renames never break compliance records.
Contributors download every CLA version they signed. Admins download current and archived versions.