WIP: Add batch revision ranges for Jujutsu #58

Closed

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

dikka commented

2026-08-02 12:01:54 +00:00

Owner

Summary

accept inclusive Jujutsu <start>--<end> revision ranges and list every resolved change before rewriting
require one confirmation by default, support -y bypass, and force single-suggestion automatic application without later prompts
process every revision independently so diff, API, parsing, and rewrite failures do not prevent later revisions from running
prefix complete per-revision console and debug blocks with accessible colors, including multiline errors
document batch usage and cover range syntax, prefixed logging, and recoverable HTTP failures

Validation

cargo test --locked --all-targets -- --test-threads=1 (51 passed)
cargo check --locked --all-targets
cargo fmt -- --check
git diff --check
end-to-end JJ range run against a local mock API: three inclusive revisions were listed; the first HTTP 500 was reported with fully prefixed multiline output; both later revisions were still requested and successfully rewritten; the command returned failure after completing all three
pseudo-terminal confirmation run: the complete range and confirmation prompt were displayed, declining exited successfully, made no API requests, and left all descriptions unchanged

Related issue: lab/turboCommit#55

## Summary - accept inclusive Jujutsu `<start>--<end>` revision ranges and list every resolved change before rewriting - require one confirmation by default, support `-y` bypass, and force single-suggestion automatic application without later prompts - process every revision independently so diff, API, parsing, and rewrite failures do not prevent later revisions from running - prefix complete per-revision console and debug blocks with accessible colors, including multiline errors - document batch usage and cover range syntax, prefixed logging, and recoverable HTTP failures ## Validation - `cargo test --locked --all-targets -- --test-threads=1` (51 passed) - `cargo check --locked --all-targets` - `cargo fmt -- --check` - `git diff --check` - end-to-end JJ range run against a local mock API: three inclusive revisions were listed; the first HTTP 500 was reported with fully prefixed multiline output; both later revisions were still requested and successfully rewritten; the command returned failure after completing all three - pseudo-terminal confirmation run: the complete range and confirmation prompt were displayed, declining exited successfully, made no API requests, and left all descriptions unchanged --- Related issue: lab/turboCommit#55

dikka added 2 commits

2026-08-02 12:01:54 +00:00