![]() Run the installer for 2.3.1, close it when you get the blank login window. To proceed with this method:ĭelete the Atlassian folder from the AppData/Local directory for your user. In the meantime, and as a workaround, you can collect the accounts.json and passwd files from a working install. Feel free to vote for it or add your comment, you can also watch the ticket to receive further updates. We're tracking feedback for this feature at SRCTREEWIN-6935. The team announced that they're working on creating an Enterprise installer for Sourcetree for Windows, which will be an MSI compatible with systems management software such as System Center Configuration Manager, support silent and offline installs, and allow the administrator to choose the installation folder. But because it's always synced with github, I'm not worried about that.Hi Kevin! Currently, there's not an offline installer available. This gives me two things, a Linux development environment (yay!) and in the event I need to, I simply destroy the virtual box, and everything is gone, website and all. In my setup, I actually have an instance of ubuntu running in a virtual box on my windows 10 work machine. So you shouldn't have to specifically add the remote, it should be done automatically.Īnd yes, from your work machine anytime git needs to do something to authenticate through github, it will ask for your login credentials unless you add the ssh keys to your github account. The nice part is though, when you clone the remote repo to your work machine, git will automatically set up the remote URL's, and they will point to the repo you cloned, which is what you're going to want. Than I get home, rinse and repeat.(pull, work, commit, push). I work on it on my laptop at home, and I always do a "nightly push" before going to bed, so when I get to work, and I want to work on the project on my work machine (guilty too), I just pull the changes down, work, commit, push back. You can follow this: to check for existing ssh keys on your computer, and than follow the links at the bottom of the page to either generate new ssh keys, or add your existing keys to your github account. That's okay, but because both of my computers are pretty secure to me, I set up ssh keys on both computers, so I'm auth'ed through them, allowing me to just simply push. (Note: when entering your password in the terminal, it will not show any characters, not even ***, so although it looks like you are typing nothing, you are typing your password) Cloning the repo should set up your upstream and downstream correctly, but it never hurts to check.Īs far as auth goes, git will ask for your github username and password each time you try to push to the remote repo. ![]() You can follow Luke's advice to setting or resetting your remote if you need to. Make sure on both computers, your pull and push streams are your remote, which you can expose by typing git remote -v. Than on the next computer, pull in my changes before starting, and continue. I pull in changes before I start, work, and commit changes when I'm done. I do exactly what you're talking about, I work from two different computers, pushing and pulling from the remote repo on both. ![]() And I never did much with branches, since it was only me, but like you, I've decided to play around with branches even though on small, solo, projects it adds unnecessary complexity, it's all about learning how to integrate into larger, team based projects were branches are necessary for the future. I'm just actually about a few weeks ahead of you, in coding on two different computers, so I'm just sharing my experiences. In regards to your push error, I've never had it, so see if this doesn't fix it: I would also highly recommend reading this: Than when you get to computer2, you can fetch and merge, or pull (which is a fetch and merge done automatically by git) the remote branch, and continue your work on it.Ĭheck out the accepted answer on this one: Make sure to push to the branch by git push origin branch-name before closing down. Than when I see a nightly commit, I know it's not a good bookmark, and it's certainly not complete. ![]() Often times if my stopping point is time, (like bedtime) and not a ready to go point, i personally just decided to call those commit messages (nightly commit ). If you were done for the night on computer1, you want to make sure you push it to the remote branch so you have access to it on computer2. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |