The scheduled close-issues workflow in VRSEN/agentswarm-cli fails because the script targets the upstream repo instead of the fork repo.
Evidence:
- Recent failed run: https://github.com/VRSEN/agentswarm-cli/actions/runs/26380910844
.github/workflows/close-issues.yml runs script/github/close-issues.ts with the fork repo token.
script/github/close-issues.ts hard-codes anomalyco/opencode, so the fork token does not have permission to comment on or close those issues.
Expected behavior:
- In GitHub Actions, the stale-issue script should target
GITHUB_REPOSITORY.
- Local fallback behavior should target
VRSEN/agentswarm-cli when GITHUB_REPOSITORY is absent, not upstream.
The scheduled
close-issuesworkflow inVRSEN/agentswarm-clifails because the script targets the upstream repo instead of the fork repo.Evidence:
.github/workflows/close-issues.ymlrunsscript/github/close-issues.tswith the fork repo token.script/github/close-issues.tshard-codesanomalyco/opencode, so the fork token does not have permission to comment on or close those issues.Expected behavior:
GITHUB_REPOSITORY.VRSEN/agentswarm-cliwhenGITHUB_REPOSITORYis absent, not upstream.