<commit_before>---
layout: single
title:  "Git Repo"
sidebar:
  nav: reference
---

**The Git Repo artifact is available in version 1.17 or later.**
{: .notice--info}

{% include toc %}

Git Repo artifacts are references to Git repositories that are hosted by a Git hosting service. They are consumed
by stages that need multiple files to produce an output, such as the Bake (Manifest) stage when using the Kustomize template
renderer. Unlike other artifact implementations, the Git Repo artifact works with any Git hosting service as long as the
repository can be cloned using the Git CLI.

## Git Repo artifact in the UI

The pipeline UI exposes the following fields for the GitHub file artifact:

| Field | Explanation |
| ------|--------------|
|Account| A Git Repo artifact account. |
|URL| HTTP or SSH URL of your Git repository. Use HTTP for artifact accounts configured to use a username and password, and use the SSH URL format for accounts configured to use the SSH private key. |
|Branch| Name of the branch to check out. Default is `master`. |
|Sub Path (Optional) | Relative path of files within the repository to fetch. If set, only files this path will be available to stages consuming this artifact. |

### In a trigger

_Work to support Git Repo artifacts in triggers is currently underway._

### In a pipeline stage

When configuring the "Bake (Manifest)" stage, you can use a Git Repo artifact as an expected artifact.

{%
    include<commit_msg>Changing Github for Git Repo (#2079)<commit_after>---
layout: single
title:  "Git Repo"
sidebar:
  nav: reference
---

**The Git Repo artifact is available in version 1.17 or later.**
{: .notice--info}

{% include toc %}

Git Repo artifacts are references to Git repositories that are hosted by a Git hosting service. They are consumed
by stages that need multiple files to produce an output, such as the Bake (Manifest) stage when using the Kustomize template
renderer. Unlike other artifact implementations, the Git Repo artifact works with any Git hosting service as long as the
repository can be cloned using the Git CLI.

## Git Repo artifact in the UI

The pipeline UI exposes the following fields for the Git Repo artifact:

| Field | Explanation |
| ------|--------------|
|Account| A Git Repo artifact account. |
|URL| HTTP or SSH URL of your Git repository. Use HTTP for artifact accounts configured to use a username and password, and use the SSH URL format for accounts configured to use the SSH private key. |
|Branch| Name of the branch to check out. Default is `master`. |
|Sub Path (Optional) | Relative path of files within the repository to fetch. If set, only files this path will be available to stages consuming this artifact. |

### In a trigger

_Work to support Git Repo artifacts in triggers is currently underway._

### In a pipeline stage

When configuring the "Bake (Manifest)" stage, you can use a Git Repo artifact as an expected artifact.

{%
    include
{'fraction_non_alphanumeric': 0.07355932203389831, 'fraction_numerical': 0.003389830508474576, 'mean_word_length': 3.8218954248366015, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '6816099', 'n_tokens_mistral': 801, 'n_tokens_neox': 731, 'n_words': 454}