Problem
tl_gh_issue_close_batch fails when closing 20+ issues at once. The tool builds a single GraphQL mutation with all close + comment operations, which exceeds GitHub's query size limit.
Reproduction
tl_gh_issue_close_batch --repo edimuj/app-chat-game --issues 1214,1213,1212,...(23 total) --reason "not planned" --comment "Closing as stale..."
The generated mutation contains 2 operations per issue (closeIssue + addComment), so 23 issues = 46 mutation fields in one request. GitHub rejects it.
Expected behavior
The tool should chunk large batches into smaller GraphQL mutations (e.g., 10 issues per request) and aggregate results.
Workaround
Fall back to gh issue close in a shell loop:
for issue in 1214 1213 ...; do gh issue close $issue -R owner/repo -r "not planned" -c "comment"; done
Context
Encountered while bulk-closing 23 stale game review findings under an umbrella issue. The first batch partially succeeded (closed ~14 issues) before the error, leaving the operation in an inconsistent state — some issues closed, some not.
Problem
tl_gh_issue_close_batchfails when closing 20+ issues at once. The tool builds a single GraphQL mutation with all close + comment operations, which exceeds GitHub's query size limit.Reproduction
The generated mutation contains 2 operations per issue (closeIssue + addComment), so 23 issues = 46 mutation fields in one request. GitHub rejects it.
Expected behavior
The tool should chunk large batches into smaller GraphQL mutations (e.g., 10 issues per request) and aggregate results.
Workaround
Fall back to
gh issue closein a shell loop:Context
Encountered while bulk-closing 23 stale game review findings under an umbrella issue. The first batch partially succeeded (closed ~14 issues) before the error, leaving the operation in an inconsistent state — some issues closed, some not.