-
Adjust your PATH environment variable so that Git and optional UNIX tools can be used from the Windows command prompt. To do so, select this option in the Git installer:
Observação:
Since Windows 10 version 1803, Microsoft has added native SSH support, which is known to cause conflict with Git connections. If your Windows version is higher than 1803, ensure that the path to SSH binaries in the Git installation (C:\Program Files\Git\usr\bin) takes precedence over the path to SSH binaries provided by Microsoft (%SystemRoot%\system32). You can access the system PATH environment variable through the System Properties dialog box > Advanced tab > Environment Variables.
-
to select your external diff/merge application such as p4merge.-
Observação:
If the connection profile is to be used to upload the currently open RoboHelp project to your Git server, the new repository URL must be empty. While creating the repository, ensure that you do not initialize it with a readme file.
-
In the SSH Private Key field, specify or navigate to the path of the SSH private key that you use for connecting to the repository on your Git server. To set up a new SSH connection to your Git server, see Set up an SSH connection.
Observação:
If the specified SSH key contains a passphrase, RoboHelp prompts you to enter this passphrase and saves it in the system Credential Manager for subsequent use. The record is stored in this format:
git@<servername>:<orgName/repoName>/<user>
If you are using a new SSH key for connection to the same repository but with a different passphrase, delete or update the corresponding record in the system Credential Manager. If RoboHelp does not find a matching record in the system Credential Manager, it prompts for the passphrase again. For more information about system Credential Manager (Windows), see Microsoft Help.If the key is successfully added to the SSH agent running on your system and the connection to the specified Git server is successful using this key, a confirmation prompt appears. The Save button is enabled only if this step is successful. Otherwise, verify the connection setup by referring to Set up an SSH connection.
-
In the Local Path field, specify a path on your computer that maps to the repository on the server.
If the connection profile is to be used to upload the currently open RoboHelp project to your Git server, specify the folder containing the project or any of its parent folders. The local Git repository is initialized in this folder and is published to your Git server.
Otherwise, to use the connection profile to clone a repository from your Git server, provide the path to an empty local folder in which the repository is to be cloned. If the specified path does not exist, it is created before cloning.
-
Create an SSH key pair (public and private) using GitBash. For more information, see Git Help.
-
In RoboHelp, choose Collaborate > Open Connection and select a Git connection profile. The repository is cloned at the local path specified in the connection profile.
Observação:
If the specified local path in the connection profile already contains a Git repository, cloning is skipped.
-
In the Open dialog box, select a RoboHelp project file (.rhpj) and click Open.
RoboHelp opens the project file.
Observação:
When you open a RoboHelp project for the first time using these steps, connection information is stored inside the project for subsequent use. So directly open the project using one of the ways described in Open a project.
Add content to or edit a topic. You can quickly begin editing files without any network connection.
Also, you can do the following:
-
To commit the changes to your local repository, choose Collaborate > Commit.
The Commit dialog box opens.
To push pending commits to your Git server, choose Collaborate > Push.
If another user updated the repository on your Git server, your push operation fails. In this case, pull the latest version from the repository on the server and then retry the push operation.
Observação:
To perform the push operation, you must have write access to the repository on your Git server.
-
To sync your local repository to match the repository on the server, choose Collaborate > Pull.
If some of your local files contain edits that are not yet committed to your local repository and these files are updated on the server, the pull operation fails. In this case, commit your changes first.
-
After successfully pulling changes, files that contain both local and remote commits are merged. If the merge is unsuccessful, a merge conflict occurs and it must be resolved. To resolve merge conflicts, choose Collaborate > Commit.
In the Commit dialog box, files containing merge conflicts are indicated as
in the Action column. -
Click
against the file to merge conflicts using the external diff/merge application that you have registered in Step 3 in Prerequisites for connecting to Git. The registered diff/merge application opens for the specific file.
-
To add a project, choose Collaborate > Add Project and select a Git connection profile.
The local path in the profile must contain the current project. For more information, see Step 9 in Create a Git connection profile.
Observação:
This operation fails if the repository specified in the connection profile contains any files. To add your RoboHelp project to an existing repository on the server, first clone that repository on your system and then copy or move your project into the folder in which the repository is cloned.
-
Commit the required files as described in Commit your changes.
-
Push the commit as described in Push your changes to the server.
-
Click Ok.
When the connection is removed, RoboHelp reopens the project, and the Add Project option in Collaborate menu becomes available. To add the project again, see Add a project to your Git server.
Observação:
If you did not delete the local repository, when you add the project using the same connection profile as before, your local changes are preserved and you can commit/push them as required.
If you deleted the local repository, you cannot push changes to the repository on the server mentioned in the same connection profile as it already contains files. So you must add the project using a connection profile that contains an empty repository.
As publicações do Twitter™ e do Facebook não são cobertas pelos termos do Creative Commons.