Repository navigation
ci(fork): mirror only, without the paused gate or review requests - #91
Conversation
The gate cannot pass until records declare capture completeness, so it runs by hand only. Reviewers read the mirrored record on their normal first review; nothing posts trigger comments. The mirror also follows the bootstrap routing recorder.
|
I'll fix CI failures and address comments from users with write access that start with 'Devin'.
|
|
Note Currently processing new changes in this PR. This may take a few minutes, please wait... ⚙️ Run configuration
📒 Files selected for processing (3)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
PR Summary by QodoMake Garnet evidence mirroring independent of the paused gate
AI Description
Diagram
High-Level Assessment
Files changed (3)
|
There was a problem hiding this comment.
👀 1 finding needs your review
Devin fixed 1 of 2 findings on 76ad85d. Click a finding below to jump to its comment.
For your review (1)
Fixed by Devin (1)
- Gate header describes a paused trigger as active
Code Review by Qodo
1. Withdrawn evidence can leave a green check
|
PR Code Suggestions ✨Warning
No code suggestions found for the PR. |
|
Execution Profiles for ⏳ updates in place as each job's record lands 💡 How to read thisRunner.Worker ← process on a path
└─ npm
└─ node ← process that acted
└─ ○ npmjs[.]org ← observed action
follow a path downward to see what ran and what it did — each path to an observed action is an execution chain names on the path = processes · ○ = observed action · (…) = context |
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes using default effort and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Want higher recall? High effort reviews run extra passes and find more bugs. A team admin can switch effort levels in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 76ad85d. Configure here.
| on: # zizmor: ignore[dangerous-triggers] default branch only, no pull request code runs here | ||
| workflow_run: | ||
| workflows: ["TS CI"] | ||
| workflows: ["TS CI", "Garnet Bootstrap Routing"] |
There was a problem hiding this comment.
Mirror trigger names missing workflow
Medium Severity
The workflow_run trigger lists Garnet Bootstrap Routing, but no workflow in this repository uses that name. GitHub never emits workflow_run for an unknown workflow, so the mirror does not follow that recorder after it completes.
Reviewed by Cursor Bugbot for commit 76ad85d. Configure here.
| on: # zizmor: ignore[dangerous-triggers] default branch only, no pull request code runs here | ||
| workflow_run: | ||
| workflows: ["TS CI"] | ||
| workflows: ["TS CI", "Garnet Bootstrap Routing"] |
There was a problem hiding this comment.
🟡 Bootstrap completions never refresh evidence
When bootstrap routing finishes, Garnet Bootstrap Routing cannot trigger the mirror because no workflow has that name. Without a matching comment event, the PR description keeps its previous evidence.
Learn more
A workflow_run trigger matches the name of an existing workflow in this repository. No checked-in workflow is named Garnet Bootstrap Routing, so that completion cannot start the mirror. The separate comment trigger can still refresh the description when a trusted Runtime Review comment is created or edited, but it does not make the new completion trigger functional.
Example: A bootstrap-only run finishes while its Runtime Review comment has not generated an eligible comment event. The mirror does not start for that completion, and the description retains the prior evidence rather than refreshing from the completed run.
Recommended fix: Identify the actual workflow name of the bootstrap recorder on the default branch and use it in the workflows list. If the recorder has no workflow in this repository, remove this inert trigger or add the intended recorder before relying on completion events.
Was this helpful? React with 👍 or 👎 to provide feedback.


Summary
Fork-only CI change. The evidence mirror keeps copying the head-bound Garnet comment into the PR description from the default branch (no PR code runs). It no longer publishes
garnet/evidenceand no longer posts reviewer trigger comments or Devin API requests. Reviewers see the mirrored record on their normal first review, e.g. when a draft that recorded during CI is marked ready.garnet-evidence-mirror.yml: drop the gate and re-review steps, dropchecks: writeand the reviewer/Devin env, and also follow theGarnet Bootstrap Routingrecorder.garnet-evidence-gate.yml: paused (manualworkflow_dispatchonly). Live records do not declare capture completeness yet, so it cannot pass.garnet-evidence-mirror.mjs: the mirrored preamble no longer prescribes a citation line. It keeps the facts-only / judgment-stays-with-the-reviewer note.garnet-rereview.mjsandgarnet-evidence-gate.mjsstay in the tree, so this is easy to revert.Squash Commit Body
Checklist
actionlintclean on both workflows.Link to Devin session: https://app.devin.ai/sessions/b554fb265c3347cfb2b92892896f618d
Open in Devin Desktop: https://app.devin.ai/desktop/session/b554fb265c3347cfb2b92892896f618d?variant=devin
Requested by: @jadoonf
Need help on this PR? Tag
@codesmith-botwith what you need. Autofix is disabled.Note
Low Risk
Fork-only GitHub Actions wiring; no runtime package or auth changes, though branch protection that required
garnet/evidencewill no longer be satisfied automatically until the gate is re-enabled.Overview
Fork CI narrows Garnet evidence automation to description mirroring only—no
garnet/evidencecheck and no bot/Devin review triggers from the mirror workflow.The evidence mirror workflow now listens to
Garnet Bootstrap Routingcompletions as well asTS CI, dropschecks: writeand reviewer/Devin env, and removes the steps that rangarnet-evidence-gate.mjsandgarnet-rereview.mjs. Reviewers are expected to see the mirrored record on a normal first review (e.g. draft → ready).The
garnet/evidencegate workflow is paused for automaticworkflow_run/issue_commentruns until records declare capture completeness; it only runs viaworkflow_dispatchwith a required PR number (manual path still supports the old event shapes in the jobif).The mirror script preamble no longer includes a prescribed citation line or the blockquoted runtime-evidence format—only the facts-only / judgment-stays-with-reviewer note remains.
Reviewed by Cursor Bugbot for commit 76ad85d. Bugbot is set up for automated code reviews on this repo. Configure here.
Runtime evidence (Garnet)
No runtime evidence is bound to head
76ad85dyet. The sticky Garnet Runtime Review comment either has not been posted for this head or describes an earlier commit. Missing evidence means no record, not a clean run.