Skip to content

ci: add Jules + OpenCodeReview cloud review dispatch - #21

Open
LeoneMarcos wants to merge 4 commits into
mainfrom
chore/jules-ocr-review
Open

LeoneMarcos wants to merge 4 commits into
mainfrom
chore/jules-ocr-review

Conversation

@LeoneMarcos

@LeoneMarcos LeoneMarcos commented Sep 13, 2026

Copy link
Copy Markdown
Owner

Adds a cloud-only Jules + OpenCodeReview review pipeline.

Flow: PR event → reusable dispatch issue → jules label added with the user's GitHub identity → Jules task on the user's plan → OpenCodeReview Delegation Mode → empty Jules result PR → result relayed back to the source PR → empty artifact closed.

Safety/behavior:

  • No Jules REST API key and no model API are used.
  • Same-repository PRs only; draft PRs are skipped.
  • Jules is instructed to keep review result PRs file-empty.
  • Result PRs are auto-closed only when changed_files == 0; any unexpected code changes are left open for human inspection.
  • One dispatch issue is reused per source PR.

One-time repository setup still required: add an Actions secret named JULES_GITHUB_TOKEN containing a fine-grained GitHub PAT for LeoneMarcos, scoped to this repository with Issues: Read and write. Live testing showed that a jules label added by github-actions[bot] did not start Jules, while the same label added with the user's GitHub identity did. The PAT is used only for that label operation.

Live tests completed:

  • Jules started from issue [Jules OCR] Review PR #21 @ 880bc24 #22 using the user's plan and ran the review-only task with OpenCodeReview delegation; its result reported no critical/high/medium findings and produced empty artifact PR Review PR #21 #23.
  • Relay behavior was exercised with empty test PR Review PR #21 #24: the workflow copied the report back to this PR and auto-closed the artifact.

The Jules OCR workflow is expected to remain red until JULES_GITHUB_TOKEN is configured; normal CI is independent.

@github-actions

github-actions Bot commented Sep 13, 2026

Copy link
Copy Markdown
Contributor

Jules + OpenCodeReview review prepared for 880bc24: #22

@cloudflare-workers-and-pages

cloudflare-workers-and-pages Bot commented Sep 13, 2026

Copy link
Copy Markdown

Deploying with  Cloudflare Workers  Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status Name Latest Commit Preview URL Updated (UTC)
✅ Deployment successful!
View logs
blackjack 3b78205 Commit Preview URL

Branch Preview URL
Sep 13 2026, 11:19 PM

@LeoneMarcos LeoneMarcos mentioned this pull request Sep 13, 2026

Copy link
Copy Markdown
Owner Author

Jules + OpenCodeReview

Completed review-only code review of PR #21 using OpenCodeReview delegation mode. No critical, high, or medium findings were identified.

Test review artifact: #23

@LeoneMarcos LeoneMarcos mentioned this pull request Sep 13, 2026
@github-actions

Copy link
Copy Markdown
Contributor

Jules + OpenCodeReview

Completed review-only code review of PR #21 using OpenCodeReview delegation mode. Relay workflow test: no critical, high, or medium findings were identified.

Review artifact: #24

Copy link
Copy Markdown
Owner Author

@jules Please update this PR branch directly with these two fixes, then run a focused validation and report back here. Do not open another implementation PR.

  1. Apply the OpenCodeReview finding from PR OpenCodeReview PR Review for PR #21 #25: in the "Trigger Jules with user identity" github-script step, pass steps.prepare.outputs.issue-number through env as ISSUE_NUMBER and read Number(process.env.ISSUE_NUMBER) instead of interpolating the Actions expression directly inside JavaScript.

  2. Fix the relay matcher. Real Jules review artifact PR OpenCodeReview PR Review for PR #21 #25 is titled "OpenCodeReview PR Review for PR ci: add Jules + OpenCodeReview cloud review dispatch #21", so the current relay job condition startsWith(title, 'Review PR #') misses it. Keep the branch-prefix safety guard (chore/jules-ocr-review-) and allow the relay job to parse/validate the original PR from the artifact body/title inside the script rather than requiring that exact title prefix in the job-level condition.

After the changes, verify the YAML/logic and summarize exactly what changed.

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