We have recently begun using RoboHelp 2015 with Git and we are seeing some strange behavior when we change local repositories and then open the project in RoboHelp. As we would expect, when we change the active repository in Git we can see the project files in our local project directory change, based upon what the active repository contains. The problem is, though, when we then open the project again, after changing the active repository, RoboHelp is displaying changes from the previous active repository.
Here is an example from yesterday:
Create a new local repository called "Deleting old topics" and delete a bunch of unused topics.
Commit the changes in the local repository.
In Git, switch to the local master (or to an existing local repository that hasn't been touched in weeks).
Verify in Windows Explorer that the deleted files have returned (expected behavior because those files/topics weren't deleted in this repository).
Open the project in RoboHelp. The topics deleted in the "Deleting old topics" repository are still showing as deleted, even though we are in a different repository and have verified that the files (including the fpj files) are showing that that the topics should be there in this repository.
What we've tried thus far:
We have tried changing the preference that rebuilds the cpd file on launch: this behavior persists no matter if we rebuild the cpd or not.
Replacing the cpd file with one saved from before the topics were deleted: replacing the cpd file causes RoboHelp to see the files correctly but the fix only lasts until additional files are deleted and then the environment breaks again, as described above.
Is the problem simply that RoboHelp 2015 doesn't play nicely with Git and we need to upgrade to 2019? Are those of you with RH 2019 seeing any behavior like this or does RoboHelp 2019 properly recognize the changes that Git makes to the local environment?
I am not a source control user but I can offer two comments.
There are certain files you should not put into source control. See Snippets on my site.
I think you will find posts about GIT indicating that it did not play nicely with 2015. Search this forum and the dedicated Source Control forum. GIT is now supported in 2019 but I can't comment on whether it plays nicely.