snow-actions/Sparse checkout action
Sparse checkout a git repository
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Stale
- License
- None
Inputs
| name | description | required | default |
|---|---|---|---|
| patterns | Write a set of patterns to the sparse-checkout file. [Learn more about set](https://git-scm.com/docs/git-sparse-checkout#Documentation/git-sparse-checkout.txt-emsetem) | yes | — |
| repository | Repository name with owner. For example, snow-actions/sparse-checkout | no | ${{ github.repository }} |
| ref | The branch, tag or SHA to checkout. When checking out the repository that triggered a workflow, this defaults to the reference or SHA for that event. Otherwise, uses the default branch. | no | — |
| token | Personal access token (PAT) used to fetch the repository. The PAT is configured with the local git config, which enables your scripts to run authenticated git commands. 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) | no | ${{ github.token }} |
| path | Relative path under $GITHUB_WORKSPACE to place the repository | no | . |
| filter | Use the partial clone feature and request that the server sends a subset of reachable objects according to a given object filter. | no | "" |
Outputs
no outputs