Home/ Questions/Q 419495
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-12T18:46:59+00:00

Ok, a few things I’m not quite sure about. For starters: I have a

  • 0

Ok, a few things I’m not quite sure about.

For starters:

  • I have a “bare” repo on a VPS in a remote DC.
  • I have a workstation at work that I also code on.
  • I have a workstation at home that I also code on.

1 – When I set up my initial repo on one of my workstation (i think Git calls this the master), should I check out and work from a different directory? Like subversion.

2 – When I want to work on the code at work, I’m confused, how do I go about making commits to the LOCAL repo on my work desktop and then at the end of the day, push my changes to the “bare” repo on my VPS so that I can pull the updates to my home desktop.

I tried using clone but every push I make from my home desktop ended up w/ me pushing the changes back to the remote repo.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    1 – master is git’s default name for the main branch of a repository. It does not refer to the entire repository, but to that one line of development. You don’t need a separate working directory – the general idea of local git development is to work in the directory, commit changes to the repository, then push them upstream as necessary.

    2 – You should have a remote in both your home and work repos pointed at the bare VPS repo. If you created your repo by cloning the VPS repo, it will be ‘origin’. Pushing to and pulling from origin are the defaults, so this is why your pushes are going there. This is the designed behavior – there’s a good chance that when you clone a repo, it’s the one you want to get updates from and push your changes back to.

    I would suggest having both home and work treat the VPS repo as origin. You can then push to and pull from it on each computer when necessary, simply using git push and git pull. If one of your repos isn’t already set up this way, you could either reclone the VPS repo to do it automatically, or use

    git remote add origin <url-of-VPS-repo>
git config branch.master.remote origin
git config branch.master.merge = refs/heads/master

    The last two lines let git know that you would like your master branch to be associated with the master branch on the origin remote (your VPS).

    • 0