Add git-lfs to installed packages in Dockerfile#329
Merged
Conversation
|
Would you kindly take a look at this ? It is a small change that would help out a bunch of people who are using Git LFS. Thanks ! |
|
@anothrNick gently reminder to take a look and approve. |
urbaned121
approved these changes
Apr 24, 2025
anothrNick
approved these changes
May 7, 2025
Owner
|
@urbaned121 thanks for the ping. Approved |
Owner
|
Should be available in |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary of changes
I use Git LFS to track large files that seldomly change.
Git LFS adds some hooks to call into the
git-lfscommand.However, this command is not installed in the Docker image produced by the action, so the entire action fails.
Alternative workarounds
Adding the following step before github-tag-action can be used to circumvent the missing dependency:
Breaking Changes
Do any of the included changes break current behaviour or configuration?
I believe not, since
git-lfsis only invoked if its hooks are enabled.How changes have been tested
Docker build:
Also, the forked action was run in a private repository, where Git LFS is configured. See log extracts below.
Output before changes
Output using this PR