Skip to content

fix(list): report worktree-side renames - #4191

Merged
max-sixty merged 1 commit into
max-sixty:mainfrom
Duang777:fix/list-worktree-side-renames
Sep 19, 2026
Merged

max-sixty merged 1 commit into
max-sixty:mainfrom
Duang777:fix/list-worktree-side-renames

Conversation

@Duang777

Copy link
Copy Markdown
Contributor

Summary

  • Mark R porcelain records as renames in wt list.
  • Keep a worktree whose only change is an unstaged rename from rendering as clean.
  • Add a direct parser regression test.

Follow-up to the diff-outside observation in #4190. Kept separate so #4190 stayed at its original one-file parser scope.

Verification

  • Red check: the new test fails with the old index-column-only condition.
  • cargo test --bin wt worktree_rename_is_reported_as_dirty
  • cargo fmt --all -- --check
  • cargo clippy --all-targets --all-features -- -D warnings
  • Full suite passed 4,933/4,933 before formatting; the exact formatted rerun passed 4,932 tests and hit the unrelated existing test_alias_concurrent_receives_sigint timing failure. Clean CI is the deciding run.

@max-sixty
max-sixty merged commit bc018f3 into max-sixty:main Sep 19, 2026
38 checks passed
@max-sixty

Copy link
Copy Markdown
Owner

thanks for these @Duang777 !!

@max-sixty max-sixty mentioned this pull request Sep 20, 2026
max-sixty added a commit that referenced this pull request Sep 20, 2026
0.79.0 was prepared and merged in #4181 but never tagged, so it never shipped.
Cargo.toml and Cargo.lock already carry the version, so this reuses it and folds
the thirteen commits that landed since into the same changelog section.

New entries cover the worktree-side rename fixes (#4190, #4191), the per-project
unknown-field warning (#4123), and the unterminated code fence in the picker's
preview (#4183, combined with #4178's column fix).

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants