Skip to content

ci(cla): report dispatched CLA pass via commit status#206

Open
teamchong wants to merge 1 commit into
cloudflare:mainfrom
teamchong:ci/cla-dispatch-commit-status
Open

ci(cla): report dispatched CLA pass via commit status#206
teamchong wants to merge 1 commit into
cloudflare:mainfrom
teamchong:ci/cla-dispatch-commit-status

Conversation

@teamchong

@teamchong teamchong commented Jul 4, 2026

Copy link
Copy Markdown
Collaborator

#204 wasn't enough. When cla.yml runs via workflow_dispatch, the run's check suite lands on the commit with associated_prs=0, so it never attaches to the release PR. The run goes green but the merge box never sees a CLAssistant check and the PR stays blocked on the required status check.

This keeps everything from #204 (trigger, validation guard, dispatch from release.yml) and only changes how the result is reported. After the guard passes, the workflow posts a commit status with context CLAssistant on $GITHUB_SHA. Statuses attach to the SHA directly, so they show up in the PR status rollup and satisfy the required check even with the ruleset pinned to the GitHub Actions app. No new permissions, the workflow already had statuses: write.

Tested end to end on my fork instead of experimenting here. Mirrored the ruleset (required status check CLAssistant pinned to the GitHub Actions app) and had a throwaway workflow open a fake release PR shaped like a real one, opened by github-actions[bot] from changeset-release/main with a bot-authored head commit so it passes the guard: teamchong#2. Before the fix it sat at mergeStateStatus: BLOCKED with an empty rollup, same as the incident here. Then I dispatched it the same way release.yml does (gh workflow run cla.yml --ref changeset-release/main -f pull_request=2, run: https://github.com/teamchong/capnweb/actions/runs/28710748911) and it flipped to mergeable: true with CLAssistant: success in the rollup.

@changeset-bot

changeset-bot Bot commented Jul 4, 2026

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: 200c4b0

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@pkg-pr-new

pkg-pr-new Bot commented Jul 4, 2026

Copy link
Copy Markdown

Open in StackBlitz

npm i https://pkg.pr.new/cloudflare/capnweb@206

commit: 200c4b0

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