I opened a review with a few changesets. The reviewer asked me to rename some files to fit with the coding standards we have.
I use mercurial rename to rename it properly (hg mv) so mercurial is aware of the rename and commit it. TortoiseHG displays: fileY.sql (was renamed from fileX.sql).
After that I commited a few syntax fixes to the files.
Add the changesets to the review. Now under the files view of the review the old files still exist. Kiln reviews have no awareness of file renames!
What this means is other reviewers will be reviewing the wrong files. We end up just creating a new review with half the changesets. This is just totally useless and costs people their time.
It's confusing when file renames are involved... do I really have to patch all the commits into another branch?!
Perhaps you can put a note on the fileY label saying it was renamed from fileX.
Kiln Version 188.8.131.52