On Tue, 8 Nov 2022 at 15:41, Jeff King <peff@xxxxxxxx> wrote: > > On Tue, Nov 08, 2022 at 10:50:33AM +0000, M Hickford wrote: > > > Secondly, the docs recommend git-credential-cache [2] which ships with > > Git and is equally easy to configure. So why isn't it more popular? My > > hypothesis: while caching works great for passwords typed from memory, > > the combination of caching with personal access tokens has poor > > usability. The unmemorised token is lost when the cache expires, so > > the user has to generate a new token every session. I suspect GitHub's > > 2021 decision to stop accepting passwords [4] may have inadvertently > > pushed users from 'cache' to 'store'. > > Another big problem with credential-cache is that it requires Unix > sockets, so it doesn't run on Windows. Thanks to the work of Carlo Marcelo Arenas Belón [1], credential-cache *can* be built on Windows 10 April 2018 update or later. But Git for Windows has to support older Windows versions for many more years so the build flag can't be enabled. Perhaps Git for Windows could ship with a credential-cache binary that works on Windows 10 and gracefully degrades on older Windows versions? That's beyond my expertise. Help very welcome at https://github.com/git-for-windows/git/issues/3892 Might this be suitable for a GSoC project? If a mentor could be found. [1] https://lore.kernel.org/git/20210914072600.11552-1-carenas@xxxxxxxxx/
