feat: allow up to eight parallel GitHub tasks - #93
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What Changed
scheduler run --concurrencyto select 1–8 independent GitHub tasks, retaining the default of 2.Why
The requested configurable parallel execution must use the current GitHub-native scheduler. This branch is reconciled with main's native worktrees, task checkpoints, scope admission, recovery, and guarded automatic merge. The superseded SQLite scheduler changes are removed from the final diff.
How to Test
bun run typecheckandbun run lint; both must pass.bun run test; the complete suite must pass.bun dev scheduler run --help; concurrency must show 1–8 with default 2.--concurrency 0,9, or a fraction; the CLI must reject the argument before execution.Acceptance checklist
test/scheduler/github-pool.test.ts.Additional Notes
The added eight-slot coverage is deterministic; no live eight-provider run is claimed. Conflicting or ambiguous scopes remain exclusive even when spare slots exist. Auto-merge remains opt-in and is serialized independently of task concurrency. No application PR was merged during this conflict resolution.