lscm list changes subcommand returns old path for move state after parent path was changed
FolderA was change to FolderB and list changes result is like this:
Changeset A:
"new-path": "\Folder1\FolderB\",
"path": "\Folder1\FolderA\",
"state": {
"add": false,
"conflict": false,
"content_change": false,
"delete": false,
"move": true,
"potential_conflict": false,
"property_change": false
}
After that, the list changes subcommand for a move state of a file under the same folder returns old path:
Changeset B:
"new-path": "\Folder1\FolderB\NewSubFolder\FileX.txt",
"path": "\Folder1\FolderA\FileX.txt",
"state": {
"add": false,
"conflict": false,
"content_change": false,
"delete": false,
"move": true,
"potential_conflict": false,
"property_change": false
}
The correct path should be: "path": "\Folder1\FolderB\FileX.txt",
Another change set for the same file with 'content_change' state was working and return the correct new path.
"path": "\Folder1\FolderB\NewSubFolder\FileX.txt",
"state": {
"add": false,
"conflict": false,
"content_change": true,
"delete": false,
"move": false,
"potential_conflict": false,
"property_change": false
}
This happened when I did a migration from RTC to Gitlab, I need to get all change sets from RTC replicate them in git commits.
Here is my lscm version:
Build Id: EWM-CLIENT-I20220731-0234
Version: 7.0.2
Thanks.
|