-
Notifications
You must be signed in to change notification settings - Fork 165
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
LFS File Locks & 'check out' issues #120
Comments
Well sorry for the disturbance, the solution in #109 worked for me : I had put my email instead of my git user name in the "uses Git LFS 2 file locking workflow" text box. |
Fix this issue with the previous comment, look #109 . |
I got this exact error on gitlab, username is the same as in gitlab, I also tried using the email as "User to lock files" but didn't work. |
Yup, as I said, email does not work. I'd suggest you to check that you made no mistake with your user name (including lower / upper case), it's really what solved the issue in my case. |
I get this issue as well on 4.25 (w/ Azure DevOps). Weirdly, it says it fails but then it actually works if I check |
Hello,
I try to use this for testing with Bitbucket.
But, there seem to be fundamental issues with file-locking.
i.e. when I do the following (from UE, but similar beahviour in UE if Git-Bash is used for locking).
Set a lock:
which then outputs:
SourceControl: Locked Content/A/B.uasset
So that's a success. Seemingly.
After which the file has been locked succesfully in the git world, but - UE Source Control then errors with:
LogSlate: Window 'Unable to Check Out From Source Control!' being destroyed
And file save attempts trigger a warning that the file is writable, but " not checked Out From Source Control".
So - to try to get to the bottom of the issue, and since a "check-out" is a perforce/sub-version concept, and not one that Git has: After successfully setting a git lfs lock (which is achieved succesfully here in git), what else would be needed for UE Source Control and/or the Git Plugin (2.14 beta) to succesfully check-out a file from git/bitbucket...?
(also, for the person that set the lock, the file is then write-accessible - yet, UE complaints about the file not being 'checked out')
Cheers.
The text was updated successfully, but these errors were encountered: