name: 'Checkout'description: 'Checkout a Git repository at a particular version'inputs:repository:description: 'Repository name with owner. For example, actions/checkout'default: ${{ github.repository }}ref:description: >The branch, tag or SHA to checkout. When checking out the repository thattriggered a workflow, this defaults to the reference or SHA for thatevent. Otherwise, uses the default branch.token:description: >Personal access token (PAT) used to fetch the repository. The PAT is configuredwith the local git config, which enables your scripts to run authenticated gitcommands. The post-job step removes the PAT.We recommend using a service account with the least permissions necessary.Also when generating a new PAT, select the least scopes necessary.[Learn more about creating and using encrypted secrets](https://help.github.com/en/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)default: ${{ github.token }}ssh-key:description: >SSH key used to fetch the repository. The SSH key is configured with the localgit config, which enables your scripts to run authenticated git commands.The post-job step removes the SSH key.We recommend using a service account with the least permissions necessary.[Learn more about creating and usingencrypted secrets](https://help.github.com/en/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)ssh-known-hosts:description: >Known hosts in addition to the user and global host key database. The publicSSH keys for a host may be obtained using the utility `ssh-keyscan`. For example,`ssh-keyscan github.com`. The public key for github.com is always implicitly added.ssh-strict:description: >Whether to perform strict host key checking. When true, adds the options `StrictHostKeyChecking=yes`and `CheckHostIP=no` to the SSH command line. Use the input `ssh-known-hosts` toconfigure additional hosts.default: truessh-user:description: >The user to use when connecting to the remote SSH host. By default 'git' is used.default: gitpersist-credentials:description: 'Whether to configure the token or SSH key with the local git config'default: truepath:description: 'Relative path under $GITHUB_WORKSPACE to place the repository'clean:description: 'Whether to execute `git clean -ffdx && git reset --hard HEAD` before fetching'default: truefilter:description: >Partially clone against a given filter.Overrides sparse-checkout if set.default: nullsparse-checkout:description: >Do a sparse checkout on given patterns.Each pattern should be separated with new lines.default: nullsparse-checkout-cone-mode:description: >Specifies whether to use cone-mode when doing a sparse checkout.default: truefetch-depth:description: 'Number of commits to fetch. 0 indicates all history for all branches and tags.'default: 1fetch-tags:description: 'Whether to fetch tags, even if fetch-depth > 0.'default: falseshow-progress:description: 'Whether to show progress status output when fetching.'default: truelfs:description: 'Whether to download Git-LFS files'default: falsesubmodules:description: >Whether to checkout submodules: `true` to checkout submodules or `recursive` torecursively checkout submodules.When the `ssh-key` input is not provided, SSH URLs beginning with `git@github.com:` areconverted to HTTPS.default: falseset-safe-directory:description: Add repository path as safe.directory for Git global config by running `git config --global --add safe.directory <path>`default: truegithub-server-url:description: The base URL for the GitHub instance that you are trying to clone from, will use environment defaults to fetch from the same instance that the workflow is running from unless specified. Example URLs are https://github.com or https://my-ghes-server.example.comrequired: falseallow-unsafe-pr-checkout:description: >Required to check out fork pull request code from a workflow triggered by`pull_request_target` or `workflow_run`. These workflows run with thebase repository's GITHUB_TOKEN, secrets, default-branch cache scope, andrunner access; fetching and executing a fork's code in that trustedcontext commonly leads to "pwn request" vulnerabilities. Set to `true`only after reviewing the risks at https://gh.io/securely-using-pull_request_target.default: falseoutputs:ref:description: 'The branch, tag or SHA that was checked out'commit:description: 'The commit SHA that was checked out'runs:using: node24main: dist/index.jspost: dist/index.js