WIP: Add batch revision rewriting for Jujutsu #59

Closed

dikka wants to merge 2 commits from agent/issue-55-jj-batch-revisions into main

dikka commented

2026-08-02 14:26:27 +00:00

Owner

Summary

support inclusive Jujutsu ancestry ranges with a single confirmation and -y bypass
imply automatic single-suggestion handling and generate descriptions concurrently
continue draining the batch after diff, API, rewrite, or diagnostic-output failures
emit captured diagnostics and results in revision-labelled blocks with unique, contrast-tested labels
preserve stable change IDs, inclusive merge-aware ordering, existing descriptions, and user instructions
document batch usage and add focused parser, ordering, diagnostics, warning-capture, and accessibility tests

Validation

cargo fmt --check
cargo check
cargo test --all-targets -- --test-threads=1 (55 passed)
cargo clippy --all-targets (completed with existing repository warnings)
git diff --check

Not verified

End-to-end execution against the jj CLI was not run because jj is not installed in the prepared environment.
Live OpenAI batch requests were not run; API behavior is covered through the existing request tests and focused batch-path unit tests.

Related issue: lab/turboCommit#55

## Summary - support inclusive Jujutsu ancestry ranges with a single confirmation and `-y` bypass - imply automatic single-suggestion handling and generate descriptions concurrently - continue draining the batch after diff, API, rewrite, or diagnostic-output failures - emit captured diagnostics and results in revision-labelled blocks with unique, contrast-tested labels - preserve stable change IDs, inclusive merge-aware ordering, existing descriptions, and user instructions - document batch usage and add focused parser, ordering, diagnostics, warning-capture, and accessibility tests ## Validation - `cargo fmt --check` - `cargo check` - `cargo test --all-targets -- --test-threads=1` (55 passed) - `cargo clippy --all-targets` (completed with existing repository warnings) - `git diff --check` ## Not verified - End-to-end execution against the `jj` CLI was not run because `jj` is not installed in the prepared environment. - Live OpenAI batch requests were not run; API behavior is covered through the existing request tests and focused batch-path unit tests. --- Related issue: lab/turboCommit#55

dikka added 2 commits

2026-08-02 14:26:27 +00:00