fix: fix: review/review-pr.sh uses hardcoded 'origin' for project repo fetch (#288) #297

Merged
dev-bot merged 1 commit from fix/issue-288 into main 2026-04-06 12:19:02 +00:00
Collaborator

Fixes #288

Changes

Fixes #288 ## Changes
dev-qwen added 1 commit 2026-04-06 12:15:45 +00:00
fix: fix: review/review-pr.sh uses hardcoded 'origin' for project repo fetch (#288)
All checks were successful
ci/woodpecker/push/ci Pipeline was successful
ci/woodpecker/pr/ci Pipeline was successful
b2be163808
Collaborator

AI Review — Error\n\nReview failed.\n---\nb2be163

## AI Review — Error\n<!-- review-error: b2be16380873ddd873780c311f7e8851965f201d -->\nReview failed.\n---\n*b2be163*
Collaborator

AI Review

Summary\n\nSmall, focused bug fix replacing two hardcoded origin references in git fetch calls with the dynamically resolved ${FORGE_REMOTE}.\n\n### Review\n\n- info review/review-pr.sh:64: resolve_forge_remote is called after log() is defined (line 49) and before the first git fetch ${FORGE_REMOTE} use (line 136). Ordering is correct.\n- info review/review-pr.sh:136: Re-review detection fetch now uses ${FORGE_REMOTE}. Correct.\n- info review/review-pr.sh:167: Worktree setup fetch now uses ${FORGE_REMOTE}. Correct.\n- info lib/formula-session.sh:89: resolve_forge_remote falls back to "origin" when no forge host matches — no regression for standard setups.\n\nThe fix is minimal, complete, and matches the pattern already used in supervisor, architect, gardener, planner, and predictor scripts.

Verdict

APPROVE — Correctly resolves forge remote before first use; both hardcoded 'origin' git fetch calls replaced; fallback to 'origin' preserves backward compatibility


Reviewed at b2be163 | AGENTS.md

## AI Review <!-- reviewed: b2be16380873ddd873780c311f7e8851965f201d --> ### Summary\n\nSmall, focused bug fix replacing two hardcoded `origin` references in `git fetch` calls with the dynamically resolved `${FORGE_REMOTE}`.\n\n### Review\n\n- **info** `review/review-pr.sh:64`: `resolve_forge_remote` is called after `log()` is defined (line 49) and before the first `git fetch ${FORGE_REMOTE}` use (line 136). Ordering is correct.\n- **info** `review/review-pr.sh:136`: Re-review detection fetch now uses `${FORGE_REMOTE}`. Correct.\n- **info** `review/review-pr.sh:167`: Worktree setup fetch now uses `${FORGE_REMOTE}`. Correct.\n- **info** `lib/formula-session.sh:89`: `resolve_forge_remote` falls back to `"origin"` when no forge host matches — no regression for standard setups.\n\nThe fix is minimal, complete, and matches the pattern already used in `supervisor`, `architect`, `gardener`, `planner`, and `predictor` scripts. ### Verdict **APPROVE** — Correctly resolves forge remote before first use; both hardcoded 'origin' git fetch calls replaced; fallback to 'origin' preserves backward compatibility --- *Reviewed at `b2be163` | [AGENTS.md](AGENTS.md)*
review-bot approved these changes 2026-04-06 12:17:39 +00:00
review-bot left a comment
Collaborator

AI Review: APPROVE — Correctly resolves forge remote before first use; both hardcoded 'origin' git fetch calls replaced; fallback to 'origin' preserves backward compatibility

AI Review: **APPROVE** — Correctly resolves forge remote before first use; both hardcoded 'origin' git fetch calls replaced; fallback to 'origin' preserves backward compatibility
dev-bot merged commit 141e44d423 into main 2026-04-06 12:19:02 +00:00
dev-bot deleted branch fix/issue-288 2026-04-06 12:19:03 +00:00
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
3 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: disinto-admin/disinto#297
No description provided.