WIP: Add batch Jujutsu revision ranges #63

Draft

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

dikka commented

2026-08-12 12:08:52 +00:00

Owner

Why

Allow descriptions for a contiguous Jujutsu ancestor range to be generated and rewritten in one confirmed operation.

What

Adds <start>--<end> range handling with confirmation/--yes, concurrent per-revision generation, ordered rewrite application, and accessible revision-prefixed result and debug-log blocks. Individual preparation, request, and rewrite failures do not stop remaining revisions.

Validation

git diff --check and git fsck --no-reflogs --no-dangling passed. A fresh independent read-only final audit completed with Verdict: GO. Cargo tests and JJ integration tests were not run because this workspace image has neither cargo/rustc nor jj; the audit confirmed those tools are unavailable. The parser implication unit test covers forced batch auto-apply and one suggestion.

Notes

Batch descriptions are applied in resolved range order after concurrent requests complete, using stable Jujutsu change IDs so descendants resolve after rebasing. Batch debug/context records are buffered and emitted in the matching revision block; shared debug files append records during a batch. End-to-end JJ range and logging integration coverage remains a follow-up.

Related issue: lab/turboCommit#55

## Why Allow descriptions for a contiguous Jujutsu ancestor range to be generated and rewritten in one confirmed operation. ## What Adds `<start>--<end>` range handling with confirmation/`--yes`, concurrent per-revision generation, ordered rewrite application, and accessible revision-prefixed result and debug-log blocks. Individual preparation, request, and rewrite failures do not stop remaining revisions. ## Validation `git diff --check` and `git fsck --no-reflogs --no-dangling` passed. A fresh independent read-only final audit completed with `Verdict: GO`. Cargo tests and JJ integration tests were not run because this workspace image has neither `cargo`/`rustc` nor `jj`; the audit confirmed those tools are unavailable. The parser implication unit test covers forced batch auto-apply and one suggestion. ## Notes Batch descriptions are applied in resolved range order after concurrent requests complete, using stable Jujutsu change IDs so descendants resolve after rebasing. Batch debug/context records are buffered and emitted in the matching revision block; shared debug files append records during a batch. End-to-end JJ range and logging integration coverage remains a follow-up. --- Related issue: lab/turboCommit#55

dikka added 2 commits

2026-08-12 12:08:52 +00:00

feat: batch jj revision ranges 6b2ef21f69

fix: preserve batch debug logs bf0bd03889

This pull request is marked as a work in progress.

View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.

git fetch -u origin agent/issue-55-batch-jj-revisions:agent/issue-55-batch-jj-revisions

git switch agent/issue-55-batch-jj-revisions

Merge

Merge the changes and update on Forgejo.

Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.

git switch main

git merge --no-ff agent/issue-55-batch-jj-revisions

git switch agent/issue-55-batch-jj-revisions

git rebase main

git switch main

git merge --ff-only agent/issue-55-batch-jj-revisions

git switch agent/issue-55-batch-jj-revisions

git rebase main

git switch main

git merge --no-ff agent/issue-55-batch-jj-revisions

git switch main

git merge --squash agent/issue-55-batch-jj-revisions