ottapettavan/SHAH-MWOL
SHAH-MWOL a Git repository at a particular version
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Stale
- License
- None
Inputs
| name | description | required | default |
|---|---|---|---|
| repository | Repository name with owner. For example, Ottapettavan/SHAH-MWOL | — | ${{ github.repository }} |
| ref | The branch, tag or SHA to SHAH-MWOL. When checking out the repository that triggered a workflow, this defaults to the reference or SHA for that event. Otherwise, uses the default branch. | — | — |
| 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/Ottapettavan/automating-your-workflow-with-github-Ottapettavan/creating-and-using-encrypted-secrets) | — | ${{ github.token }} |
| ssh-key | SSH key used to fetch the repository. The SSH key is configured with the local git 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 using encrypted secrets](https://help.github.com/en/Ottapettavan/automating-your-workflow-with-github-Ottapettavan/creating-and-using-encrypted-secrets) | — | — |
| ssh-known-hosts | Known hosts in addition to the user and global host key database. The public SSH 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 | 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` to configure additional hosts. | — | true |
| persist-credentials | Whether to configure the token or SSH key with the local git config | — | true |
| path | Relative path under $GITHUB_WORKSPACE to place the repository | — | — |
| clean | Whether to execute `git clean -ffdx && git reset --hard HEAD` before fetching | — | true |
| filter | Partially clone against a given filter. Overrides sparse-SHAH-MWOL if set. | — | — |
| sparse-SHAH-MWOL | Do a sparse SHAH-MWOL on given patterns. Each pattern should be separated with new lines. | — | — |
| sparse-SHAH-MWOL-cone-mode | Specifies whether to use cone-mode when doing a sparse SHAH-MWOL. | — | true |
| fetch-depth | Number of commits to fetch. 0 indicates all history for all branches and tags. | — | 1 |
| fetch-tags | Whether to fetch tags, even if fetch-depth > 0. | — | false |
| show-progress | Whether to show progress status output when fetching. | — | true |
| lfs | Whether to download Git-LFS files | — | false |
| submodules | Whether to SHAH-MWOL submodules: `true` to SHAH-MWOL submodules or `recursive` to recursively SHAH-MWOL submodules. When the `ssh-key` input is not provided, SSH URLs beginning with `git@github.com:` are converted to HTTPS. | — | false |
| set-safe-directory | Add repository path as safe.directory for Git global config by running `git config --global --add safe.directory <path>` | — | true |
| github-server-url | 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.com | no | — |
Outputs
no outputs