![]() I'm quite disappointed with this engineering decision, but even more so, the fact they haven't corrected what I along with most other people on this thread think is an obnoxious interference into how experienced developers work. In fact, I've also signed up for a small corporate plan on GitHub and have moved most of my new work there instead of BitBucket, so that I can more effectively use GitHub Desktop or their GUI for Pull Request management, something prompted largely due to this irritation. Full console output showed that this wouldn’t work as you can’t put a submodule into a tracked folder. Interestingly, I couldn’t add an empty folder to the working set, so I dropped a test file into the folder and tried again. But to be honest, until they restore an ability for me to use MY OWN NAMING CONVENTION for the dozens of ssh keys I have to deal with, I have no interest in giving them another chance. SourceTree didn’t like this as now there was a new folder in the repo that hadn’t been added to the tracked list. Good to know symlinks work, should I ever decide to give these guys a chance again. That's the reason I haven't come back here since my original post, until getting another message today from this thread and getting curious. There should be a way to specify the location of an existing ssh key!Īnother option, and the one I chose, is to switch to Github Desktop, as I really don't like a software vendor who breaks existing, widely-expected intuitive behavior without warning, and then ignores customer complaints about it for months. Not letting me use my existing ssh key is a recipe for losing me as a customer - I don't like being forced to change the way I work. Why can't I use the ssh key which I want to use? Why isn't this finding my default ssh key like all other programs I have which use ssh, including earlier versions of SourceTree. ![]() Now, I see no way to specify this key, it's not being found despite being in the normal location on Mac/Linux systems, and it seems the only way to use ssh is to generate a new ssh key - WHICH I DO NOT WANT TO DO. I used to be able to use this with SourceTree. Now, I get a message "no key found", despite the fact I have ~/.ssh/id_rsa defined, it's in my agent and Apple keychain, and I can use this fine everywhere else. Before, I could pick one of my ssh keys (I have dozens, but mainly use one for work and another for personal Git repos) during setup. It seems there is some change to how the setup and configuration of SSH keys work. I'm on a new project where I have to collaborate with some people on Windows and suggested they use SourceTree, and wanted to re-install SourceTree on my macs so I could help them learn this by demonstration, as I have used this from time to time in the past. I normally use the command line git client to work with GitHub or BitBucket. The following web page explains what push and pull really do.I just rebuilt my laptop and iMac with clean installs of MacOS Sierra. ![]() The above web page is part of a useful chapter that is introduced here: The following web page explains more about what commit really does. ![]() Pull is what merges other peoples changes into the files you have modified (but not pushed) and what copies the changes others have made to files you have not modified. I thought that Commit makes your changes visible to other people, but I was wrong. This means that Commit does not modify the remote repository by itself, only when you do a Push at the same time or at a later time as a Commit. Staged means that you have marked a modified file in its current version to go into your next commit snapshot. Modified means that you have changed the file but have not committed it to your database yet. Committed means that the data is safely stored in your local database (repository). Git has three main states that your files can reside in: committed, modified, and staged. This is the main thing to remember about Git if you want the rest of your learning process to go smoothly. The major difference between Git and any other VCS (version control system) (Subversion and friends included) is the way Git thinks about its data. Here are some highlights from the above page: It includes a discussion of: The major difference between Git and any other VCS (version control system). I found the following web page to be very useful.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |