1. To open your project, start HCL OneTest API and then click Browse to navigate to the project in the local repository.
   Note: Ensure that you have completed the setup listed in Prerequisites.
2. Look at the status bar for the icons that indicate connectivity to the Git repository. Use the following table to interpret the icons displayed.

   Icon	Description
   	No Git repository exists that contains the project opened in HCL OneTest API. The project files exist only in the local repository.
   	The Git repository exists but is not connected.
   	The Git repository exists and is connected.

3. Check for the status of the files in the project contained in the local and remote Git repositories from the Status bar. Use the following table to interpret the status displayed.

   Icon	Description
   	The master branch in the Git repository exists but is not connected.
   	The master branch in the Git repository exists and is connected.
   	The master branch in the Git repository exists and is connected. The status of the files in the repositories is shown with numbers prefixed with colored arrows. The green colored arrow () indicates the local repository and the red colored arrow () indicates the remote Git repository. Both the green and red arrows together () indicate a file conflict state between the files in the local and files in the remote repositories.
   	The number along with the green colored arrow indicates the files on the local repository that are modified with respect to the same files on the remote Git repository.
   	The number along with the red colored arrow indicates the files on the remote Git repository that are modified with respect to the same files on the local repository.
   	The number along with both the green and red colored arrows indicates the files with a potential conflict. A conflict is displayed when the same file has changes made by you in the local repository and has also been changed by someone else on the remote repository. You must resolve this conflict by either merging the changes or rejecting the changes in the remote version. You must resolve this conflict outside of HCL OneTest API by using the Git commands or any other method you prefer.

4. Hover your cursor over the Git icon and numbers to view the location of the Git repository connected to HCL OneTest API displayed as a tooltip:
   
5. Click the area with the Git icon and numbers, to view the details of the files in the repositories and files that are in conflict. The Git Information window is displayed as shown in the following sample image.
   

   The details of the files in the local repository that are modified with respect to the files in the remote repository are shown in the following table.

   Status	Description
   Local	The details of the files in the local repository.
   Ahead	The details of the files in the local repository that are modified with respect to their version on the remote Git repository. The files in the local repository have changes that are not committed or pushed to the remote repository.
   Behind	The details of the files in the remote Git repository that are modified with respect to their version on the local Git repository. The files in the remote repository have changes that are not yet pulled into the local repository.

Checking status in the Test Factory or Architecture School perspective views

6. Check for the status of the files in the project contained in the local and remote Git repositories by looking at the icons prefixed to the test asset in the Test Factory or Architecture School perspective views. Use the following table to interpret the displayed icon prefixed to the test asset.

   Icon	Description
   	The file in the local repository that is changed from the file in the remote Git repository. For example, the icon displayed for a changed file in the Test Factory perspective is .
   	The file in the remote Git repository that is changed from the file in the local repository. For example, the icon displayed for a changed file in the Test Factory perspective is .
   	The file is in conflict means that the file has changes made by you in the local repository and the same file has also been changed by someone else on the remote repository. For example, the icon displayed for a changed file in the Test Factory perspective is .

Before you begin

Before you can update the files in a project in a Git repository, certain tasks must be completed:

• You must have set up the Git repositories.
• The project files must exist in the local repository.
• You must have opened the project from the local repository.

Tip: You can check if the repository is connected by looking at the Git icon () displayed in the Status bar. For interpreting the Git icons and numbers displayed, see Checking the status of files in repositories.

1. From the Menu, click Tools > Update Project.

   The Update Project window is displayed.

   

   The sample window shown in the following image is displayed if there are files in a conflict state in the local and remote repositories.

   

   If you proceed with updating the project, the files in the local repository that are in the conflict state are overwritten by the files from the remote repository. If you want to retain the changes in your local version of the file and merge the changes from the remote file version, you must perform the merge operation outside of HCL OneTest API by using your preferred Git method.

2. Click OK to pull the files from the remote Git repository to your local repository.
   Note: This action discards uncommitted changes in your project files and replaces them with the files in the project from the remote Git repository.

Before you begin

Before you can deliver changes in the project files to the remote Git repository, certain tasks must be completed:

• You must have set up the Git repositories.
• The project files must exist in the local repository.
• You must have opened the project from the local repository.
• You must have made changes in the project for the files to show as changed in the HCL OneTest API UI.

Tip: You can check if the repository is connected by looking at the Git icon () displayed in the Status bar. For interpreting the Git icons displayed, see Checking the status of files in repositories.

1. To use the Menu option, complete the following steps:
   1. From the Menu, click Tools > Deliver changes. The changed files are listed as selected in the Deliver changes window as shown in the following sample image.
      Note: Using the Menu option to deliver changes selects all the files that have changed in the project. You can deselect or select the files you want to deliver by clicking the check box.
      
   2. In the Deliver changes window, enter text in the Commit Message box.
   3. Click OK.
2. To use the Git options in the Logical View (Tree View) of the Architecture School perspective, complete the following steps:
   1. Open the Logical View in the Architecture School perspective and select the tree view.
   2. Select the test asset that contains the changed file, right-click and click Deliver changes. You can identify the changed file if it is prefixed with the icon (). See the following example image. The changed files are listed as selected in the Deliver changes window as shown in the following example image.
      
      Note: Using the Git menu option to deliver changes selects only the files under that test asset that you selected.
      
   3. In the Deliver changes window, enter text in the Commit Message box.
   4. Click OK.
3. To use the Git options in the Test Factory perspective, complete the following steps:
   1. Select the test asset that contains the changed file, right-click and click Deliver changes. You can identify the changed file if it is prefixed with the icon (). See the following example image. The changed files are listed as selected in the Deliver changes window as shown in the following example image.
      
      Note: Using the Git menu option to deliver changes selects only the files under that test asset that you selected.
      
   2. In the Deliver changes window, enter text in the Commit Message box.
   3. Click OK.
4. To use the Git options in the Physical View of the Architecture School perspective, complete the following steps:
   1. Open the Physical View, select the test asset, right-click and click Deliver changes. You can identify the changed file if it is prefixed with the icon (). See the following example image.
      
      The changed files are listed as selected in the Deliver changes window as shown in the following sample image.
      Note: Using the Git menu option to deliver changes selects only the files under that test asset that you selected.
      
   2. In the Deliver changes window, enter text in the Commit Message box.
   3. Click OK.

Before you begin

Before you can update the files in a project in a Git repository, certain tasks must be completed:

• You must have set up the Git repositories.
• The project files must exist in the local repository.
• You must have opened the project from the local repository.
• You must have made changes in the project for the files to show as changed in the HCL OneTest API UI.

Tip: You can check if the repository is connected by looking at the Git icon () displayed in the Status bar. For interpreting the Git icons displayed, see Checking the status of files in repositories.

1. To use the Menu option, complete the following steps:
   1. From the Menu, click Tools > Undo Changes. The changed files in the local repository are listed as selected in the Undo changes window as shown in the following sample image.
      
   2. In the Undo changes window, click OK.
2. To use the Git options in the Logical View (Tree View) of the Architecture School perspective, complete the following steps:
   1. Open the Logical View in the Architecture School perspective and select the tree view.
   2. In the tree view, identify the files that are changed and uncommitted files in the project, which are prefixed with the icon (). For example, if you have created a copy of a test and have not yet checked in the project files into the remote Git repository, the changed asset is displayed with the prefixed icon as shown in the following sample image.
      
   3. Select the test asset that contains the changed file, right-click and click Undo changes. The changed files are listed as selected in the Undo changes window as shown in the following sample image.
      Note: Using the Git menu option to undo changes selects only the files under that test asset that you selected.
      
   4. In the Undo changes window, click OK.
3. To use the Git options in the Test Factory perspective, complete the following steps:
   1. In the Test Factory perspective, identify the files that are changed and uncommitted files in the project, which are prefixed with the icon (). For example, if you have created a copy of a test and have not yet checked in the project files into the remote Git repository, the changed asset is displayed with the prefixed icon as shown in the following sample image.
      
   2. Select the test asset that contains the changed file, right-click and click Undo changes. The changed files are listed as selected in the Undo changes window as shown in the following sample image.
      Note: Using the Git menu option to undo changes selects only the files under that test asset that you selected.
      
   3. In the Undo changes window, click OK.
4. To use the Git options in the Physical View of the Architecture School perspective, complete the following steps:
   1. Open the Physical View, identify the files that are changed and uncommitted files in the project, which are prefixed with the icon (). See the following example image.
      
   2. Select the test asset that contains the changed file, right-click and click Undo changes. The changed files are listed as selected in the Undo changes window as shown in the following sample image.
      Note: Using the Git menu option to undo changes selects only the files under that test asset that you selected.
      
   3. In the Undo changes window, click OK.

1. From the Menu, click Project > Preferences.
2. Click Git in the Preferences window. The Git preferences that you can configure is displayed as shown in the following screen.
   
3. To set up the Git repository in the bare mode, complete the following steps:
   1. Click the Enable bare mode check box.
   2. Enter the location of the Git repository that you want to set up as a bare directory. Alternatively, click Browse and navigate to the directory to select it.
      Note: Use this option if you are setting up a bare Git directory without the project files. If you are setting up a local repository, you must load the project files into the local repository using your preferred method in Git before you open the project in HCL OneTest API.
   3. Enter the location you want to use as the working directory or click Browse to navigate to the location.
4. To set up your user credentials to enable access to the remote Git repository from HCL OneTest API click the Git credentials check box. Enter your username and password that was set for the remote Git repository in the corresponding fields.
5. Click Apply to apply the Git preferences you set, and then click OK to save and exit from this window.