Question

So I’ve created a git repository, set up some tags and remotes on my working copy, and then pushed the repository to my server with

git push --mirror my.remote.repository

Supposedly, pushing with git –mirror will also push the remotes that I’ve set up.

However, if I do

git clone my.remote.repository

I don’t see the remotes that I created originally. Do I need special syntax to also clone the remotes? Does mirror not actually send remotes? Where did I go wrong?

Edit: Maybe my workflow is weird: Here’s what I’m trying to accomplish.
The repo is initially a clone of another project(A) that I don’t control, where I’ve renamed the remote to ‘upstream’. I’ve made a new ‘master’ branch, and intend to make changes to my working copy and deploy them. I will occasionally pull updates from the original repository (A) (switching to the original, unmodified branch and pulling from upstream). However, I’m working with other people, all of whom should be able to do this as well. The goal is to update the master branch with bug fixes from the initial repository(A) and commit the changes to the ‘master’ branch. Because of this, when a developer clones the repository, they should be inheriting the upstream branch so that they can actually do this. In short, I’m trying to use an ‘upstream’ branch to pull in updates from a different project. I haven’t used a submodule to do this since the ‘upstream’ branch actually is responsible for 95% of the files in the repository and the entire project makes no sense without the files from upstream.

Answer 1

(This isn’t a typical workflow, but I’ll try to answer the direct question anyway…)

git push --mirror will indeed have pushed your remote-tracking branches to the same name on the remote. However, when you clone, you by default only get the refs under refs/heads, which are mapped to remote-tracking branches under refs/remotes/origin/. You could clone with git clone --mirror to get the remote-tracking branches from the remote as well, but that option implies --bare.

If you want a repository with a working tree whose branches are mirrored from the remote, you could always change the refspec in the config option remote.origin.fetch to fetch every ref to the same name, but again I suspect that the real problem is that you’re using a very unusual workflow.

Incidentally, even if you use one of those techniques to change the mapping of the refs that are fetched, this won’t clone the remotes themselves, which are defined in the repository’s git config – git clone doesn’t clone anything from .git/config, which is considered to contain private information.