Files deleted from vault importing into Git as not deleted

[jackmott]

We are finding that any files/folders that were deleted in Vault are being imported into Git as if they are still present and up to date. Is this a known issue? Is there a workaround?

[robe070]

(previously submitted by me as different user) This is not an issue with my version of Vault2Git. Mine is a branch directly from Andrey's so if thats what you have I'm surprised its occurring. I have made changes to deletions, renames and moves to speed up the conversion on large repositories, but it was working before those changes too.

[jfking]

For any who come across this, we could not find the source of the problem, but we came up with a pretty easy solution. If you set your new Git repo as your Vault working folder, then delete all the contents of the Git repo (except of course the .git folder), you can then tell Vault to repopulate the folder with Get Latest. This will add back in all of the files you want, and none that have been previously deleted from Vault. Git doesn't track time stamps, so it should just recognize the deletions, which you can bundle up in one commit. This should work as long as your Git and Vault haven't diverged (i.e. do it immediately after the transfer).

[brianacraig]

So I too ran into this problem, and I was using robe070's version of vault2git. That said, I was able to solve it by making sure that the "Convertor.WorkingFolder" setting ends with a trailing slash.

Whenever it did not end with a trailing slash, the string replacement line ItemPath1.Replace(vaultRepoPath, WorkingFolder, StringComparison.CurrentCultureIgnoreCase) would end up missing a slash between the working folder and the first folder in the Vault repository. Thus the file could not be found, and it wasn't deleted.

[robe070]

@brianacraig Can you submit a pull request for this?

[robe070]

...to robe070 of course