-
Notifications
You must be signed in to change notification settings - Fork 89
feat: attempt git lfs after cloning #959
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: dev
Are you sure you want to change the base?
Conversation
|
All contributors have signed the CLA ✍️ ✅ |
|
I have read the CLA Document and I hereby sign the CLA |
|
recheck |
|
@eranturgeman or @eyalk007 Could you have a look here please. This would greatly benefit our use case and not affect other functionality |
|
hey @antikaspar , can you please explain what is the use case? |
|
closing this pr as it is become stale |
|
Probably futile now but: in projects managed with |
|
Hey @eyalk007 can you please re-open the pr or provide some feedback how we should tackle this? Thanks! |
This PR adds an optional key
lfsCheckoutto the frogbot-config that can be used with the git- parameters. This should serve as a workaround (e.g. in yarn projects) since the go git-client doesn't support git lfs commands. By setting above parameter totruefrogbot attempts to use the host installation ofgitto perform agit lfs pullafter cloning the repository.