> For the complete documentation index, see [llms.txt](https://developer.harness.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.harness.io/harness-platform/use-harness-platform/git-experience/import-input-sets.md).

# Import an input set from Git

Harness input sets are collections of runtime inputs for a pipeline provided before execution.

All pipeline settings can be set as runtime inputs in Pipeline Studio's Visual or YAML editors.

Before running a pipeline, you can select one or more input sets and apply them to the pipeline.

You can either [create an input set](/harness-platform/use-harness-platform/pipelines/input-sets.md) or import one from your Git repo.

This topic explains how to import an input set from your Git repo and apply it to your pipeline.

### Before you begin <a href="#before-you-begin" id="before-you-begin"></a>

* [Harness Git Experience Overview](/harness-platform/use-harness-platform/git-experience/git-experience-overview.md)
* [Harness Git Experience Quickstart](/harness-platform/use-harness-platform/git-experience/configure-git-experience-for-harness-entities.md)
* [Input sets and overlays](/harness-platform/use-harness-platform/pipelines/input-sets.md)
* [Manage a Harness Pipeline Repo Using Git Experience](/harness-platform/use-harness-platform/git-experience/manage-a-harness-pipeline-repo-using-git-experience.md)
* [Manage input sets and triggers in Git Experience](/harness-platform/use-harness-platform/git-experience/manage-input-sets-in-simplified-git-experience.md)

### Import an input set <a href="#import-an-input-set" id="import-an-input-set"></a>

You can import an Input Set from the CI or CD module in Harness.

This topic shows you how to import an Input Set to the CD module.

1. Select your project, select **Pipelines**, then select a pipeline.
2. In the Pipeline Studio, select **Input Sets**.
3. Click **New Input Set** and select **Import From Git**.

   ![](/files/GUCFTmkRDh3ddIAc426K)

   The **Import Input Set From Git** settings appear.

   ![](/files/0R31fMEWgsmxezo5QKTj)
4. Enter a **Name** for your Input Set.
5. Harness fetches the following details and auto-fills them:
   1. **Git Connector** (Only required if you are using a third-party Git provider)
   2. **Repository**
   3. **Git Branch**
6. Enter the **YAML Path** from where you want to import the Input Set. Make sure that your YAML path starts with `.harness/` and the YAML file already exists in the specified Git repo and branch.
7. Click **Import**.\
   Click on your **Run Pipeline** to proceed.

{% hint style="info" %}
If you use triggers to run pipelines and need the input set fetched from a specific Git branch (such as a PR source branch), you can define the `inputSetBranchName` property in your trigger YAML. For details, go to [Define the input set branch for trigger-based executions](/harness-platform/use-harness-platform/pipelines/input-sets.md#define-the-input-set-branch-for-trigger-based-executions).
{% endhint %}