Prevent git to push to wrong remote

I have a local branch “gh” that I always want to push to my account on github; I also have another local branch “lab” that I always want to push to my organization’s account on github.
I have setup two remotes (gh and lab) for that.

$ git remote -v
gh  git@Ninguem.github.com:Ninguem/prj.git (fetch)
gh  git@Ninguem.github.com:Ninguem/prj.git (push)
lab git@Ninguem.github.com:lab-rasparta-org/prj.git (fetch)
lab git@Ninguem.github.com:lab-rasparta-org/prj.git (push)

I’m afraid to inadvertently mess the two when pushing. Is there a way to prevent that?
Note:
I’ve already fetched the two successfully, so I thing they’re somehow “linked” together correctly… how do I manage what branches are “linked” to what remote branches and is there a safety mechanism?

  • Git push failed “fatal: 'origin' does not appear to be a git repository fatal: Could not read from remote repository”
  • Pushing to a remote GitHub repository
  • git push: Push all commits except the last one
  • Git reset and forced push
  • git push: when does it create the dst?
  • Does cf push respect the use of .gitignore?
  • Pull from Git Bare Repository Doesn't Have Pushed Commits
  • Git Push Server doesn't update working branch
  • 2 Solutions collect form web for “Prevent git to push to wrong remote”

    I noticed you might be confusing the terms branch and remote:

    • A remote Remote repositories are versions of your project that are hosted on the Internet or network somewhere.

    • A branch let’s you create an isolated environment for making changes in a repository.


    I believe you’re trying to avoid confusion between pushing to the wron remote.

    So suppose you have a branch my_branch in your personal GitHub account.

    The safer way to ensure the remote you’re working with is to explicitly say what remote are you pushing to:

    • If you want to push to your personal repository:

      git push gh my_branch
      
    • If you want to push to your organization’s repository:

      git push lab working_branch
      

    It will be his pattern:

    git push <remote> <remote_branch>


    You could also set up a local branch to track the remote branch on your remote gh like this:

    git checkout -b my_branch -t gh/my_branch
    

    Hope this helps.

    If you really want to avoid messing things out, then you could consider working with two local repos, each cloning a specific branch:

    • one cloning Ninguem.github.com:Ninguem/prj.git
    • one cloning Ninguem.github.com:lab-rasparta-org/prj.git

    That way, you are sure you are not in the wrong branch, or pushing to the wrong remote.

    Git Baby is a git and github fan, let's start git clone.