Repository navigation
ci: record remi verdicts through a dispatched workflow - #135
Conversation
…sion proxy allows
The proxy Claude sessions use refuses commit status writes ("Write access to
this GitHub API path is not permitted through this proxy"), so layer 4's curl
never worked from a cloud thread; #132's verdict had to be posted from remi.
remi-verdict.yml (workflow_dispatch, write access only) posts remi-proof for a
PR's exact current head, refusing anything else, with a "remi verdict:"
description. remi-proof.yml leaves those standing like a person's, and counts
remi-verdict.yml as a judge file. CONTRIBUTING layer 4 gives the gh and curl
dispatch commands.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01DYHHin9QGaqhRGgxvTT8Ju
Signed-off-by: Claude <noreply@anthropic.com>
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
github-actions
Bot
added
the
needs-claude-review
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: ee496040e2
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
|
Claude sign-off at
The review raised three low-severity notes, none blocking:
The one Codex thread (the Generated by Claude Code |
2 participants
Requested by Peter · project thread
Before: CONTRIBUTING layer 4 told cloud Claude threads to record a remi verdict with a direct
POST /statusesthrough their API proxy. The proxy refuses that path ("Write access to this GitHub API path is not permitted through this proxy", 403). #132 had to have its verdict posted from Peter'sghon remi.After: any session with write access records a verdict by dispatching
remi-verdict.yml. The proxy allows workflow dispatch, and it already worked for re-judging #127. The workflow postsremi-proofon the PR's exact current head with a "remi verdict:How:
remi-verdict.ymlruns on workflow_dispatch only. Only people with write access can start it, the same people who could post the status themselves. It never touches remi.remi-proof.ymlnow leaves a github-actions[bot] status standing when its description starts with "remi verdict:", just as it does for a person's. Its own statuses never use that prefix.remi-verdict.ymljoins the judge files (CHECKS), so changing it needs a verdict too.gh workflow runand curl dispatch commands, and keeps the directgh apistatus write for people with their own token.Tested the recorder's script against the live API with the POST stubbed. #132's real head records; a zero SHA is refused as not the head; a bad state is refused. actionlint is clean.
End-to-end check of #125 on #132 (merged): the classifier posted pending ("it changes .github/workflows/gate.yml"). Peter's account then posted success, and branch protection let it merge.
This PR changes
remi-proof.yml, so it needs a recorded verdict itself, posted from Peter's account (the new recorder only exists after merge).🤖 Generated with Claude Code
https://claude.ai/code/session_01DYHHin9QGaqhRGgxvTT8Ju
Generated by Claude Code