I’ve started a project which requires using RoboHelp 2019 Classic to update some files. (We haven’t upgraded to RoboHelp 2020 and probably won’t for a while longer.) There have been some source control errors due to files that are in source control that should not be. (We use TeamForge.)
So far I’ve found in particular that $rhvariable$.htm and <file_name>.ldb should not be in source control:
Then the following file types are also listed as those that should not be in source control:
Am I missing anything? Any other files relevant for a RoboHelp 2019 Classic project that shouldn’t be in source control?
That's the bulk. Most of those files aren't added if you use the built in source control functions in RH, but I assume you're managing the check-in/out using TeamForge. In which case, you might also avoid other htm files starting with $, as those are related to previewing topics. Mostly they should be cleaned up automatically when the preview is closed, but sometimes they aren't.
I'm not sure if you've decided to source control your output, but if you've decided not to, then also don't add the !SSL! folder, which contains generated output. (I personally don't advise source controlling output, but some companies are adamant 🙂 )
Thanks for the reply! Yes, I'm using TeamForge to check-in/out.
I read some of the Adobe information about the RH source control features. It seems to be emphasized as a safeguard when there are multiple authors on a team. If there are other advantages you've noticed, I'd be interested to hear about them.
Why would you go through the hassle of source control if you didn't have multiple authors??
Mainly I'm interested in finding out about the possible benefits of RH source control. The help files that are stored in TeamForge are more accessible to our division in TeamForge than having to ask someone else in our large organization to retrieve them from the server for publishing if the tech writer isn't available and something urgent comes up. We're also having to negotiate what substantial changes in our systems that could be temporary depending on how the pandemic unfolds, and there may be a need to revert back to an earlier state quickly. There have been times in the past where there have been multiple authors and there may be multiple authors again as well.
I'm actually a fan of source control, even for a single writer, assuming the organisation you're in already has a source control system - trying to support source control by yourself as a writer is Not Fun(tm) and I do not recommend.
That's my two cents.
Well, there you go - multiple authors (potentially) & backup. I've always been a lone author with a good backup regime, so I fall into the source control No Fun™ crowd. Even with the one project that had 2 of us, we worked on opposite sides of the planet, so just zipping it up & sticking it in a shared folder worked fine - I think Peter has referred to this method of handing off as the "hot potato" model.😁