|`stage`| Parent group of this step. See[using stages]({{site.baseurl}}/docs/pipelines/stages/) for more information.| Optional|

|`working_directory`| The directory to which the repository is cloned. It can be an explicit path in the container's file system, or a variable that references another step. The default value is {% raw %}`${{main_clone}}`{% endraw %}, but note that the default will only be used if you name your step`main_clone`. See the example on[working inside the cloned directory]({{site.baseurl}}/docs/example-catalog/ci-examples/git-checkout/#working-inside-the-cloned-directory) for more information.| Default|

|`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|

|`repo`|Thepath of the repository without the domain name in the form of`my_username/my_repo`. {::nomarkdown} <br>Note: To clone a GitHub wiki, specify the full URL of the wiki,{:/} for example,`"https://github.com/wikis/examples.wiki"`.| 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|