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.
Git commit changes to new branch how to#
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 kommentar(er)
