Add optional git-lfs support to default checkout
- Dominant language
- Python
- Stars
- 19
- Forks
- 7
- Avg merge
- 2d 9h
- Merged PRs (30d)
- 70
Description
### 📝 Description of the feature
## Feature Request: Optional Git LFS Support for Default Checkout Action
### Description
It would be helpful to add an optional parameter that enables Git LFS support during the default checkout process for repositories with large files requiring LFS.
Example usage:
```yaml
- uses: ansys/actions/
with:
git-lfs: true
```
Default value:
```yaml
git-lfs: false
```
### Expected Behavior
When `git-lfs` is enabled, the action should perform the equivalent of a `git lfs pull` (or otherwise ensure that all LFS-managed files are downloaded and available) after the repository checkout.
### Motivation
Many repositories rely on Git LFS for large assets. Currently, users need to add the checkout step manually with that option and provide `checkout: false` option. Providing built-in support through an optional parameter would simplify workflows while preserving the current behavior by default.
### 💡 Steps for implementing the feature
_No response_
### 🔗 Useful links and references
_No response_
Contributor guide
Research direction
Start by locating the default checkout action and its input definitions, then inspect how the checkout step is invoked. Confirm how existing checkout options are passed through and how Git LFS is available in the action environment; done means git-lfs defaults to false and enabled workflows obtain their LFS-managed files without requiring a separate checkout step.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, github-actions
- Domain
- ci-cd, devops
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100