fix: cron agents (gardener, planner, architect, predictor) never set FORGE_REMOTE #278
Labels
No labels
action
backlog
blocked
bug-report
in-progress
prediction/actioned
prediction/dismissed
prediction/unreviewed
priority
tech-debt
underspecified
vision
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: disinto-admin/disinto#278
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Problem
Only dev/dev-agent.sh (line 261) dynamically resolves FORGE_REMOTE by matching FORGE_URL hostname against git remotes. All *-run.sh scripts (gardener, planner, architect, predictor, supervisor) never set it and rely on the ${FORGE_REMOTE:-origin} fallback.
When the repo has multiple remotes (origin, codeberg, github, forgejo), the fallback to origin may not point to the Forge instance. The gardener at line 131 even hardcodes
git fetch origininstead of using FORGE_REMOTE.Fix
Add FORGE_REMOTE resolution to formula-session.sh (since all *-run.sh source it). Use the same pattern as dev-agent.sh line 261:
Place this in formula_worktree_setup() or as a standalone helper called early in each *-run.sh.
Affected files
originwith $FORGE_REMOTE)Acceptance criteria