Add Folders to Existing Git Experience Repos

Updated 2 months ago by Michael Cretzman

When you enable Harness Git Experience in your Project, you select a repo folder as the Harness Folder (named .harness). The Harness Folder identifies where Harness should save and look for your Project's Pipelines and resources in the repo.

When you save a Pipeline or resource the Harness Folder is used. You can tell Harness to add the Pipeline or resource to a subfolder of the Harness Folder.

You can add multiple folders as Harness Folders. This allows you to save Pipelines or resources to separate .harness folders in your repo.

This topic describes how to add new .harness folders to the repo you have set up in your Project's Git Experience.

In this topic:

Before You Begin

Make sure that you've added a Source Code Manager (SCM) and enabled Harness Git Experience in your Project.


Do not enable Harness Git Experience on a Project that already has Pipelines and resources. You must enable Harness Git Experience on a new Project when you first create the Project.

This is a temporary limitation.

Step: Add a New Harness Folder

In your Project, click Project Setup, and then click Git Management.

The repos that have been added to Git Management are displayed.

Click Add Folder for the repo where you want to add a new .harness folder.

In Add new .harness folder, in Path to the Harness folder, enter the full path from the repo root to where you want to add a new .harness folder.

The folder you added when you set up the repo in Git Management is the default folder for this repo. The default folder is simply the first folder that appears in Harness Folder settings when you save a Pipeline or resource.

Select Make this a default folder for this repository to make the new folder the default folder.

When you are done, the folder setting will look something like this:

Click Add Folder.

Now the folder is listed in the repo's row in Git Management.

Now when you save a Pipeline or resource, you can select the new folder.

See Also

See Git Experience How-tos.

Please Provide Feedback