Skip to main content

Resume after human review

When the owner submits a GitHub review, the orchestrator ingests it and materializes a MERGE_APPROVAL gate at the exact PR head.

Steps​

  1. Owner reviews the PR.

  2. Owner submits APPROVED via the GitHub UI or gh pr review --approve.

  3. Owner (or autopilot) runs:

    .\scripts\goal-runner\ingest-github-review.ps1 `
      -GoalId <GOAL_ID> `
      -ReviewJsonPath <path-to-review.json>

  4. The orchestrator materializes a MERGE_APPROVAL gate with source: github-review-approval.

  5. The orchestrator re-runs and consumes the gate.

  6. The governed merge happens.

  7. The CI on main re-runs.

  8. The orchestrator emits a PRODUCTION_PROMOTION gate (if production-bound).

What if the review was a REQUEST_CHANGES?​

The orchestrator routes the goal back to REPAIR_REQUIRED with next_action_policy.on_repair.

What if the PR head moved between review and merge?​

The gate is stale. The owner must re-submit a review at the new head.