Skip to content

Add the CAA check workflow - #1

Merged
rowan-claude merged 1 commit into
mainfrom
caa-workflow
Aug 30, 2026
Merged

Add the CAA check workflow#1
rowan-claude merged 1 commit into
mainfrom
caa-workflow

Conversation

@rowan-claude

Copy link
Copy Markdown
Collaborator

Glenn ruled on 2026-08-30 that the CAA stays on the serialize repos, and goes on every open source repo from here on. This repo had no CAA workflow at all, so this adds one.

The file is netcode/.github/workflows/cla.yml copied verbatim, byte for byte: the blob hash here is the same b8d5d657 object that netcode, reliable and yojimbo already carry. It holds no repo name, no branch filter and no path filter, so nothing needed adapting. The job id caa is what names the check run, and that is the context the org ruleset "Require CAA signature" asks for: netcode PR #180 merged on 2026-08-26 with a check run named exactly caa under the workflow "Contributor Assignment Agreement". The org secret CLA_SIGNATURES_TOKEN is visible to this repo already.

No caa check will appear on this pull request. The workflow triggers on pull_request_target, which reads the workflow file from the base branch, and the base branch does not have it until this merges. It starts reporting on pull requests opened after that.

This repo is not yet under the org ruleset, so once the check does report it will not block anything. That ordering is deliberate: the emitter goes in first, and an org owner adds the repo to the ruleset afterwards. Doing it the other way round is what left serialize, serialize.go and serialize.rs with a required check and nothing to report it.

Nothing here touches LICENSE, licensing prose or package license metadata.

serialize.java had no CAA workflow. Glenn's ruling of 2026-08-30 puts the CAA on
every open source repo, so this adds the emitter here.

This is netcode's .github/workflows/cla.yml unchanged, the same blob
b8d5d65 that netcode, reliable and yojimbo carry. The file holds no repo
name, branch or path filter, so it is correct verbatim. The job id caa is
what names the check run, which is the context the org ruleset "Require
CAA signature" asks for when an org owner adds this repo to it.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@rowan-claude
rowan-claude merged commit 3be4d72 into main Aug 30, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant