Skip to content

Fix bzr file renames not being tracked#358

Open
Ludu-nuvai wants to merge 1 commit intoacaudwell:masterfrom
Ludu-nuvai:fix/bzr-track-file-renames
Open

Fix bzr file renames not being tracked#358
Ludu-nuvai wants to merge 1 commit intoacaudwell:masterfrom
Ludu-nuvai:fix/bzr-track-file-renames

Conversation

@Ludu-nuvai
Copy link

Summary

  • Fixes file renames (bzr mv) not being visualized correctly in Gource
  • When Bazaar logs a rename, it outputs R old_path => new_path. Previously this was treated as a modify on the raw string, so moves were invisible in the visualization
  • Splits rename entries into a delete of the old path and an add of the new path, matching how other VCS parsers handle renames

Fixes #38

Test plan

  • Run Gource against a Bazaar repo containing file renames (bzr mv)
  • Verify renamed files disappear from old location and appear at new location in the visualization
  • Verify normal add/modify/delete operations still work correctly

🤖 Generated with Claude Code

When Bazaar logs a file rename (bzr mv Foo Bar), the verbose log
outputs "R  old_path => new_path". Previously this was passed through
as a single modify action on a nonsensical filename. Split rename
entries into a delete of the old path and an add of the new path,
matching how other VCS parsers handle renames.

Fixes acaudwell#38

Co-Authored-By: Claude Opus 4.6 <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.

[bzr] Tracks are not tracked

1 participant