Feedback from using the template on robercano/reDeploy:
Bot-authored PRs (bot-gh.sh pr create) arrive with no assignee, so the repo owner gets no GitHub notification that a PR is waiting for review — the autonomous loop then stalls on "no-owner-review" until the owner happens to look.
Requested change
scripts/bot-gh.sh (or the PR-creation step in the orchestrator/loop docs) should assign every newly created PR to the repo owner, e.g. by appending --assignee <owner> to pr create when the caller didn't pass one. Make the owner login configurable (env var such as OWNER_LOGIN), defaulting to the repo owner.
Already applied downstream in reDeploy (bot-gh.sh auto-append + docs/USAGE.md + redeploy-pr-loop command note) — this issue is to fold it into the template so new projects get it out of the box.
Filed on behalf of the reDeploy PR-loop session, 2026-07-03.
Feedback from using the template on robercano/reDeploy:
Bot-authored PRs (
bot-gh.sh pr create) arrive with no assignee, so the repo owner gets no GitHub notification that a PR is waiting for review — the autonomous loop then stalls on "no-owner-review" until the owner happens to look.Requested change
scripts/bot-gh.sh(or the PR-creation step in the orchestrator/loop docs) should assign every newly created PR to the repo owner, e.g. by appending--assignee <owner>topr createwhen the caller didn't pass one. Make the owner login configurable (env var such asOWNER_LOGIN), defaulting to the repo owner.Already applied downstream in reDeploy (bot-gh.sh auto-append + docs/USAGE.md + redeploy-pr-loop command note) — this issue is to fold it into the template so new projects get it out of the box.
Filed on behalf of the reDeploy PR-loop session, 2026-07-03.