Skip to content

fix: use non-workflow EvalOpsBot canary fixture#102

Merged
haasonsaas merged 1 commit into
mainfrom
codex/evalopsbot-canary-marker-file
May 20, 2026
Merged

fix: use non-workflow EvalOpsBot canary fixture#102
haasonsaas merged 1 commit into
mainfrom
codex/evalopsbot-canary-marker-file

Conversation

@haasonsaas
Copy link
Copy Markdown
Contributor

Summary

  • switch the EvalOpsBot canary fixture from a generated workflow file to a plain marker file
  • keep the canary authored by github-actions so EvalOpsBot can be requested as reviewer
  • avoid requiring workflow-file write permission just to verify the requested-review relay

Test Plan

  • actionlint .github/workflows/evalopsbot-review-canary.yml
  • rerun EvalOpsBot review request canary after merge

@haasonsaas haasonsaas merged commit 64bb02a into main May 20, 2026
3 checks passed
@haasonsaas haasonsaas deleted the codex/evalopsbot-canary-marker-file branch May 20, 2026 02:00
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