Giving someone instructions to go to the command line for a GUI tool makes no sense whatsoever. To do so, click the Check out in Sourcetree button. Next open up your SourceTree, click on Remote and click on Add an account. Click on Create personal access token to complete the setup. Next check the api and readuser checkbox, it is required for SourceTree to connect to GitLab remotely. By leaving it blank, access token will never expire. 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. You are able to set an expiry date for your access token.
#Checkout in sourcetree code
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. In this Bitbucket with SourceTree 101 tutorial take a deep drive into Bitbucket and familiarize yourself with SourceTree UI to use it for any remote reposito. The most common reason for wanting to do this. The terms may be different, but they refer to the same concept that of nesting other repositories within the folder structure of your own repository. I figured it out without your instructions but did roughly the same thing. A headline feature of SourceTree 1.3 is the support for submodules (in Git) and subrepositories (in Mercurial). Thats okay because youll add some files to it soon.
#Checkout in sourcetree software
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. Start the mission Create a new repository The repository you create is going to be empty without any code in it. 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. Attaching 'sourcetree.log' output which occurs when I click the blue 'Check out in SourceTree' button. 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 kommentar(er)
