-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Update version of - Git for Windows #1611
Comments
Hello @leemacatangay , I see you also requested installation of GVFS in #1612. Could you please share some context around these tools? cc: @dscho |
That would be the replacement installer, but it's not enough for GVFS... there is another component: https://github.com/microsoft/vfsforgit/releases (which includes the VFS for Git-specific Git fork AFAIR). Taking a step back, I'm not actually sure that it makes sense to include VFS for Git; it requires a kernel driver... |
Hi @leemacatangay, I am closing this issue, please, feel free to open a new one for any other questions. |
I agree that it makes more sense to support regular Git out of the box, and not force VFS for Git on every Azure Pipeline/GitHub Action user. The best way to use VFS for Git in CI, from my perspective, is to set up your own VMs and install build agents on them. |
Thanks for reviewing.
Thanks,
/ee
…________________________________
From: Johannes Schindelin <notifications@github.com>
Sent: Friday, September 25, 2020 5:33:08 AM
To: actions/virtual-environments <virtual-environments@noreply.github.com>
Cc: Lee Macatangay <leemac@microsoft.com>; Mention <mention@noreply.github.com>
Subject: Re: [actions/virtual-environments] Update version of - Git for Windows (#1611)
I agree that it makes more sense to support regular Git out of the box, and not force VFS for Git on every Azure Pipeline/GitHub Action user.
The best way to use VFS for Git in CI, from my perspective, is to set up your own VMs and install build agents on them.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Factions%2Fvirtual-environments%2Fissues%2F1611%23issuecomment-698901956&data=02%7C01%7Cleemac%40microsoft.com%7C7e09c2f980374c651ffd08d8614f292d%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637366339900524350&sdata=G9Io09wmBnmwFS2%2FCRJUbpWlW%2FPc1pEFR0bzutVq98o%3D&reserved=0>, or unsubscribe<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAPRM36U6ESR6GAM5INQBCWTSHSEYJANCNFSM4RQXZKSA&data=02%7C01%7Cleemac%40microsoft.com%7C7e09c2f980374c651ffd08d8614f292d%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637366339900534308&sdata=P%2FbzLqknSqM3kIhwq8wXppTFGmj3Byq%2BIgLV8kPbLHg%3D&reserved=0>.
|
Tool information
Area for Triage: Git
Question, Bug, or Feature?: Feature
Virtual environments affected
Can this tool be installed during the build?
No
Tool installation time in runtime
1 minute
Are you willing to submit a PR?
Yes
The text was updated successfully, but these errors were encountered: