Add support for renamed files
Currently (at least when using SVN) when a file is renamed, the original file shows up as deleted and the new file shows up as new. The problem is that all of the bugs and comments stay with the original file (now deleted)
randyw
shared this idea
8 comments
-
Max
commented
I know this is probably not feasible for SVN, but it would be really nice for Git and Mercurial, both of which can output a patch in the Git diff style, which can express file moves and renames.
This is really important for Java developers: refactoring happens, and when a class name gets changed, the class file gets renamed. A review with a fair amount of refactoring can turn into a big mess really fast.
-
Brian Duguid
commented
Doing a review on pre-submitted change lists with Perforce that have new files that are renamed during the review process also causes this issue.
-
Garen
commented
Tracking renames is easy to do with ClearCase, but CodeCollab doesn't do it for some reason. Each file/version has a unique object-id (oid). If the name changes but the oid is the same, the file has undergone a rename, and there is no need to litter the review with multiple entries which confuses people.
-
altoidbox
commented
In Surround if I rename a file with a change list and then I try to add the change list to the review, it results in an error and I cannot add the change list. I guess I just have to add the file as a new one.
-
nathanzhenkel
commented
At the very least, there needs to be the ability for the author to make file associations manually. I would like CC to do this automatically as much as possible, but the ability to handle this sort of thing manually will probably always be useful.
-
Yes some other systems support move directly, and others support a copy/delete semantic like Subversion. This feature would include Subversion, Perforce, AccuRev, Vault, and TFS (at least).
-
AdminRoy
(Admin, Code Collaborator)
commented
No, I think we treat other SCM systems in the same way as Subversion in this regard. jasedit is right though that in Subversion there is no such thing as an atomic "Rename" - it's an add-with-history and a delete. So in a strict Subversion sense one could argue that Code Collaborator is doing the right thing. On the other hand though, it's not doing what you really meant...
-
jasedit
commented
Is this supported in other scm systems? I know svn is a bit weird for not having an actual move command, but I've gotten the impression from documentation that this is supported in other scm systems?
