Taylor Blau

Hi @tmssngr, thanks for opening this issue and sorry that you're having problems. It looks like Git LFS is executing the SSH override fine (note the `run_command:` line in the...

Hm. This seems like a bug, then -- @larsxschneider @sschuberth do either of you have thoughts?

@sschuberth I see, thanks. It sounds like we need to do something similar for v2.5.0 (or later). I'll queue this for that. @tmssngr in the meantime, can you change your...

Hi @shive, thanks for opening this issue. I think that what you're describing here is in fact not a bug. While it is true that the pointer corresponding to an...

Ah, thank you for the clarification. I think that this is indeed a bug.

Hi, Oleg. Thanks for letting us know. > We set `lfs.setlockablereadonly=true` for certain extensions and we > made `git config lfs.setlockablereadonly` return true. Just to double check, have you run...

> > Since `lfs.setlockablereadonly` is set to 'true' by default > It was explicitly set to false in our initial setup. I think that this might be why Git LFS...

> Also, Lars Schneider was able to reproduce the issue and suspected a > bug in LFS. @larsxschneider thanks for the suggestion. I'm at a loss for what else might...

> But, I am unable to edit the file after unlocked. This is likely because your client hasn't asked for the updated state of locks. Git LFS does not do...

Hi @viric, thanks for letting me know. This definitely looks like a bug to me, and I have put this on my list of things to fix before the next...