Attempting to "Collaborate using Git" (instructions in RoboHelp Help) and add/manage version control for an existing RH2019 project in a Git repo hosted in DevOps. Using the HTTPS connection method (not SSH), which per our developers, should work. Running into a RoboHelp-generated/displayed authentication error when I attempt to add the project to the connection profile (and make that initial "push" of the entire project up to the repo). The title of the dialog is "Unable to push" and the error message text is:
fatal: Authentication failed for
Where mycompanyname is my company's name, ProjectName is the name of the DevOps project, and widgethelp is the name of my DevOps repo (configured in the RH Git connection profile). Note also that this entire https path is the exact https path that DevOps provides as the repo URL.
In troubleshooting this issue, I was able to successfully add the RoboHelp project’s folders/files to a DevOps repo via GitBash (command line - "git push.."). However, this doesn't solve the issue of RoboHelp not being able to push to (and I assume pull from) the DevOps repo.
I also confirmed that my DevOps user has full read/write permissions for the repo.
RoboHelp does report success when I make a change in the project and Collaborate>Commit the changes.
Additional areas of uncertainty for me:
Copy link to clipboard
I think you're going to need to contact the RH boffins directly on this one - email@example.com.
And now all of a sudden, it's working. I can now edit a topic in RH, save the change, Collaborate>Commit, Collaborate>Push (no error; temporarily displays success message), and separately view the DevOps repo and see the updated topic there. No RH, Git, or DevOps settings were changed; still using HTTPS repo URL. Very weird.
Notes/observations about the currently functioning enviro:
I'm going to go back and attempt this for some other projects, to document the process for the rest of my team and confirm that it's a dependable/repeatable process. We'll see how that fairs, and whether I can identify a culprit. I'll update the post accordingly. In the meantime, if anyone has any additional thoughts/insights, please add them here!
Copy link to clipboard
First, a quick recap on the enviro - this part is important - b/c the solution is Git repo enviro-specific.
My Laptop/PC Environment
Git Repositories Environment
Create a personal access token in MS DevOps (with Read/Write permissions for repos). Use the PAT's auto-generated password (provided when creating the PAT) when setting up/opening your RoboHelp connection profile for the first time.