But then my engineer tells me I have to open the Terminal and type "git LFS pull". Sourcetree has buttons that say pull and push and pull LFS. Programmers don't mind typing a small book into a little window full of code to do anything, and artists like me want to know which button to push. The engineers and artists are always at war over which Source Control to use. I have been a game artist for over 14 years. Git, 2.11.x + git-lfs v1.5.2 + Git LFS Bitbucket adapter v1 Using version 1.9.10.0, and Embedded git, 2.10.2 + git-lfs v1.5.2 + Git LFS Bitbucket adapter v1ĭeveloper 2 is using system git, with versions Then I pull the repository, and get these changed files, and not sourcetree marked one of the files as changed, and wants me to check them again. When developer2 then commits these, then they are no longer LFS files in the repository (very visible in Bitbucket website). When develeoper2, pulls the repository, then he get the indexfiles, and need to do an separate Git LFS-> Pull LFS Content.īut, when doing so, sourcetree marks the files as unstaged, that is, lot of changes because they now are the fulll files, not the index files, and thus it wants you to commit these files again. When I commit files that is in that folder, they are moved to LFS. Libraries/**/* filter=lfs diff=lfs merge=lfs -text Giving someone instructions to go to the command line for a GUI tool makes no sense whatsoever.Why cant sourcetree be updated to understand LFS? It is working now, but this "chicken and the egg" problem gives any new user the feeling that SourceTree is not ready for prime time. Really all of this should be ONE Single command called "check code in for the first time" to a remote Repo. I had to checkout the remote, pull it, then rebase my local repo to it, then commit the whole thing. Now, that still won't do anything because there is still no way to directly merge the local repo you just created with the github remote repo because you can't checkout and commit the remote repo since the local repo is basically on a branch outside of SCC. So via the command line I had to do this: cd existing_folder This created the local repo which sourcetree really has no way to do natively do - and "it should"! I got it to work by dropping to the command line and doing a git init for my local folder. I figured it out without your instructions but did roughly the same thing. Exactly HOW are you supposed to do this? How do you get the first code checked-in? It kinda gives you a bad taste to immediately get stuck with new software for a common first time use scenario.Īna: It was a mess. There are only so many buttons in SourceTree and for the most part there are no more to click on that I can see. Same Error.ĭoes SourceTree have a get-init function to initialize the existing folder and source for SourceTree/Git? Scenario 2: Click Create in SourceTree, create a repository on GitHub from local Repo. I can clone the "empty" remote GitHub repository into an empty folder but that is not going to do me any code because my local repository in "MY EXISTING" folder is where the "FIRST" incarnation of the code IS. Attempt to clone the "empty" GitHub into the "real-code" local Repo gives error: Cannot Clone into Non-Empty Folder. Scenario 1: In SourceTree, click on Clone. It seems to be a bit of a chicken and the egg situation with the software. I created a project on GitHub and I'm trying to check my local repo in for the first time into the "empty" project.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |