Repository navigation
CI: Preserve upstream reviews in separate per-commit jobs - #20
Merged
Merged
Conversation
Review each incoming commit against the full merged batch in an independent bounded job, retain successful results across failed-job retries, and require complete coverage plus compatible adaptations before publishing one integration PR. Add a review-only mode to exercise real batches before publication. The full-batch review repeatedly timed out without retaining diagnostics, including with the independent watchdog: https://github.com/jool-space/joolia/actions/runs/35460534014 Assisted-by: Codex (GPT-6)
Make the handbook agree with per-commit job assignments while retaining the complete merged batch as dependency context. Assisted-by: Codex (GPT-6)
AntonOresten
enabled auto-merge
September 19, 2026 20:47
Check apply_patch as well as shell reads, and let this non-publishing probe run while a review batch is stalled. Assisted-by: Codex (GPT-6)
AntonOresten
disabled auto-merge
September 19, 2026 21:00
Keep the Actions worker outside a bounded review cgroup, retain memory and OOM counters, and let the deadline stop descendants even when they clear the environment marker. Assisted-by: Codex (GPT-6)
Two simultaneous reviews exhausted the shared 500,000-token-per-minute limit. Keep independently retained per-commit results and full merge batches, while allowing only one review request stream at a time. https://github.com/jool-space/joolia/actions/runs/35469289715 Assisted-by: Codex (GPT-6)
Constrain response identifiers to the pinned assignment and fail invalid reports in their own review job. Combine independently validated patches with three-way merging so identical shared edits do not block a batch, while retaining manual handling for conflicts. Allow a non-publishing single-commit diagnostic. https://github.com/jool-space/joolia/actions/runs/35469289715 Assisted-by: Codex (GPT-6)
Resume transient first-attempt review failures from retained per-commit results when the run finishes. Preserve the stop conditions for cancellations, manual holds, collector or publication failures, and repeated failures. https://github.com/jool-space/joolia/actions/runs/35469289715 Assisted-by: Codex (GPT-6)
AntonOresten
enabled auto-merge
September 19, 2026 21:34
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.
Upstream review could time out before opening a PR and lose the whole batch's work. Review each incoming commit against the complete merged tree in its own saved job, then combine all validated results into one integration PR and CI build. Reviews run sequentially to avoid competing for the model's token rate limit.
Validation: 63 sync-tooling tests and actionlint pass. Hosted trials exercised real reviews, preservation of ten successful results while retrying the failed assignment, and the exact-SHA schema/validator. A local replay combined and assembled the eleven-commit candidate with upstream ancestry preserved. That replay replaced one malformed report with its schema-constrained diagnostic result after verifying that only trusted sync tooling differed between the two bases; no cross-run artifact reuse was added to production. The candidate was not pushed and its source adaptations have not yet passed integration CI.
The required full build/test gate remains enforced before this workflow change can merge. The earlier logless timeout remains unexplained; a later retained failure identified API rate limiting, with no OOM event.
Observed failures: batch timeout, per-commit trial. The exact-SHA diagnostic passed.