How does version control work in RoboHelp 2019 for GIT??? In a multi-author environment, will it automatically check out and lock files that are being edited? Or will users have to manually notify each other what they're working on and/or manually merge changes when there are conflicts?
Also, is there a plan - and timeline (and if so, when?) - to deliver version control via RoboSource Control (3.1 or maybe RSC 2019????) and Microsoft SCC API (for example, Microsoft SQL Server 2017 Express)?
Based on information provided during Adobe's recent RoboHelp 2019 announcement/release webinar:
I did the following to make RoboHelp Source work with Azure DevOps Git...
To setup source control with Robohelp, perform the following actions: