-
Notifications
You must be signed in to change notification settings - Fork 164
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
Automatic checkout prompts not working (Mac OS, gittea, UE 4.22.3) #116
Comments
Here are the logs. Kind of looks like maybe this isn't implemented yet as all they are doing is refreshing status. I don't see an attempt to lock the files.
|
Hi, I should have a look at this, but I am not using LFS anymore myself, so it might take me some time to dig into it... I think it might come from a specific set of flags not well understood by the Editor (flags like IsCheckedout CanCheckout IsWritable etc.) It could be that the file is considered as Unchanged at the time where you click on the pop-up and as such it don't do anything?
To be clear, this issue is known to me in pure git (the issue is that all modified files are considered checked out by default) but should be (needs to be) fixed |
I am pretty sure UE4 only prompts when a file is read-only. |
When I modify something in a map, just like with other source control plugins, it prompts me to checkout the file. However, if I click 'check out' in the little prompt in the bottom right, it does some work, seems like it is locking the file, but never actually locks it. It also does not report any error.
I have the same result if I go up to 'source control -> check out modified files'. It seems to work for a moment, tries to lock things, but in the end it does not lock the file and no error is reported.
I am able to successfully lock files manually (by right clicking and saying 'check out') but the checking out of modified assets automatically seems to fail. I will see about sending a log of the problem too.
Just looking for some guidance on fixing this!
System Info
The text was updated successfully, but these errors were encountered: