chore(cla): pre-seed maintainer signature to break initial catch-22#28
Merged
Merged
Conversation
The CLA Assistant bot can only record signatures by committing to signatures/version1/cla.json. Branch protection requires PR review + CLA-signed status. A maintainer's own first PR would therefore block: the bot cannot commit a signature until the PR merges, but the PR cannot merge until the CLA is signed. Pre-populate signatures/version1/cla.json with the maintainer (Johnny Miller / @millerjp, user id 163300) dated 2026-04-21T07:30:00Z. Shape matches the CLA Assistant wire format exactly so any future signatures append alongside this one without schema drift. Regenerate CONTRIBUTORS.md from the updated signatures file via scripts/generate-contributors.sh — byte-equality guard (#18) continues to hold.
|
Thank you for your contribution! Before we can merge this PR, you need to sign our Contributor License Agreement. To sign, post a comment on this PR containing exactly:
The CLA is a one-time agreement that covers every future contribution you make to any AxonOps open-source project. If you have questions before signing, please open a discussion or email I have read the CLA Document and I hereby sign the CLA You can retrigger this bot by commenting recheck in this Pull Request. Posted by the CLA Assistant Lite bot. |
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Summary
Pre-populates
signatures/version1/cla.jsonwith the maintainer's signature so the CLA Assistant flow can bootstrap. Without this, the repo maintainer cannot open their own first post-#18 PR (the CLA bot would block it; the bot's signing commit needs the maintainer to have already signed).Shape
Matches the CLA Assistant wire format verbatim (same shape as
axonops/mask'ssignatures/version1/cla.json):```json
{
"signedContributors": [
{
"name": "Johnny Miller",
"id": 163300,
"comment_id": 0,
"created_at": "2026-04-21T07:30:00Z",
"repoId": 1215690488,
"pullRequestNo": 0,
"login": "millerjp"
}
]
}
```
Any future signature the bot records simply appends another object to `signedContributors` — no schema drift.
Secondary change
Regenerated `CONTRIBUTORS.md` via `scripts/generate-contributors.sh` so the `TestGovernance_ContributorsFileIsGenerated` byte-equality guard stays green.
Merge instructions
The CLA Assistant workflow (from #18) triggered on this PR will want you to sign — but you will need to bypass it for this one PR as an admin, because:
Squash-merge with admin override. The next PR you open after this one will then see you as already-signed and the CLA Assistant flow will pass cleanly — no admin bypass needed thereafter.
Post-merge:
Test plan