Jan 9, 2023 · Jan 9, 2023 · Jan 9, 2023
diff --git a/_docs/codefresh-yaml/steps/git-clone.md b/_docs/codefresh-yaml/steps/git-clone.md
 ---
 Clones a Git repository to the filesystem.

 A pipeline can have any number of git clone steps (even none). You cancheckout code from any private or public repository. Cloning a repository is not constrained to the trigger of a pipeline. You can trigger a pipeline from a commit that happened on Git repository A while the pipeline is checking out code from Git Repository B.
 A pipeline can have any number of git clone steps (even none). You cancheck out code from any private or public repository. Cloning a repository is not constrained to the trigger of a pipeline. You can trigger a pipeline from a commit that happened on Git repository A while the pipeline is checking out code from Git Repository B.

 >Notice that if you are an existing customer before May 2019, Codefresh will automaticallycheckout the code from a [connected git repository]({{site.baseurl}}/docs/integrations/git-providers/) when a pipeline is created on that repository. In this case an implicit git clone step is included in your pipeline. You can still override it with your own git clone step as explained in this page
 >Notice that if you are an existing customer before May 2019, Codefresh will automaticallycheck out the code from a [connected git repository]({{site.baseurl}}/docs/integrations/git-providers/) when a pipeline is created on that repository. In this case an implicit git clone step is included in your pipeline. You can still override it with your own git clone step as explained in this page

 ## Usage

  description: Step description
  working_directory: /path
  repo: owner/repo
  depth: 3
  git: my-git-provider
  revision: abcdef12345'
  use_proxy: false
 | `git` | The name of the [git integration]({{site.baseurl}}/docs/integrations/git-providers/) you want to use. If left empty, Codefresh will attempt to use the git provider that was used during account sign-up. Note that this might have unexpected results if you are changing your Git integrations.| Required|
 | `repo`                                     | path of the repository without the domain name in the form of `my_username/my_repo`                                                                                                                                                                                       | Required                  |
 | `revision`                                 | The revision of the repository you are checking out. It can be a revision hash or a branch name. The default value is the branch you have specified in your Git provider (e.g `master` or `main`).                                                                                                     | Default                   |
 | `depth`                                 |  The number of commits to pull from the repo to create a shallow clone. Creating a shallow clone truncates the history to the number of commits specified, instead of pulling the entire history. | Optional                   |
 | `use_proxy`                                 | If set to true the Git clone process will honor `HTTP_PROXY` and `HTTPS_PROXY` variables if present for [working via a proxy](#using-git-behind-a-proxy). Default value is `false`.                                                                                                    | Default                   |
 | `credentials`                              | Credentials to access the repository, if it requires authentication. It can an object containing `username` and `password` fields. Credentials are optional if you are using the [built-in git integrations]({{site.baseurl}}/docs/integrations/git-providers/) .                                                                                             | Optional                  |
 | `fail_fast`                                | If a step fails and the process is halted. The default value is `true`.                                                                                                                                                            | Default                   |
Original file line number	Diff line number	Diff line change
Expand Up		@@ -9,9 +9,9 @@ toc: true
		---
		Clones a Git repository to the filesystem.

		A pipeline can have any number of git clone steps (even none). You cancheckout code from any private or public repository. Cloning a repository is not constrained to the trigger of a pipeline. You can trigger a pipeline from a commit that happened on Git repository A while the pipeline is checking out code from Git Repository B.
		A pipeline can have any number of git clone steps (even none). You cancheck out code from any private or public repository. Cloning a repository is not constrained to the trigger of a pipeline. You can trigger a pipeline from a commit that happened on Git repository A while the pipeline is checking out code from Git Repository B.

		>Notice that if you are an existing customer before May 2019, Codefresh will automaticallycheckout the code from a [connected git repository]({{site.baseurl}}/docs/integrations/git-providers/) when a pipeline is created on that repository. In this case an implicit git clone step is included in your pipeline. You can still override it with your own git clone step as explained in this page
		>Notice that if you are an existing customer before May 2019, Codefresh will automaticallycheck out the code from a [connected git repository]({{site.baseurl}}/docs/integrations/git-providers/) when a pipeline is created on that repository. In this case an implicit git clone step is included in your pipeline. You can still override it with your own git clone step as explained in this page

		## Usage

Expand All		@@ -23,6 +23,7 @@ step_name:
		description: Step description
		working_directory: /path
		repo: owner/repo
		depth: 3
		git: my-git-provider
		revision: abcdef12345'
		use_proxy: false
Expand DownExpand Up		@@ -55,6 +56,7 @@ step_name:
		\| `git` \| The name of the [git integration]({{site.baseurl}}/docs/integrations/git-providers/) you want to use. If left empty, Codefresh will attempt to use the git provider that was used during account sign-up. Note that this might have unexpected results if you are changing your Git integrations.\| Required\|
		\| `repo` \| path of the repository without the domain name in the form of `my_username/my_repo` \| Required \|
		\| `revision` \| The revision of the repository you are checking out. It can be a revision hash or a branch name. The default value is the branch you have specified in your Git provider (e.g `master` or `main`). \| Default \|
		\| `depth` \| The number of commits to pull from the repo to create a shallow clone. Creating a shallow clone truncates the history to the number of commits specified, instead of pulling the entire history. \| Optional \|
		\| `use_proxy` \| If set to true the Git clone process will honor `HTTP_PROXY` and `HTTPS_PROXY` variables if present for [working via a proxy](#using-git-behind-a-proxy). Default value is `false`. \| Default \|
		\| `credentials` \| Credentials to access the repository, if it requires authentication. It can an object containing `username` and `password` fields. Credentials are optional if you are using the [built-in git integrations]({{site.baseurl}}/docs/integrations/git-providers/) . \| Optional \|
		\| `fail_fast` \| If a step fails and the process is halted. The default value is `true`. \| Default \|
Expand Down