git chaining：git push 来自本地更新的遥控器的 remotes ref。 为什么以及如何可能？

Question

I'm facing weird (IMO) issues with my repo and start to question what I assumed. That is chaining of repos. Web search "git chaining repos" gave https://serverfault.com/questions/186161/possible-to-chain-git-repos where the answer "yes, of cause".

Now I just did git push origin HEAD:refs/remotes/origin/main in local (1st repo), in .git/config of 1st there is URL for origin (2nd repo).

In that 2nd repo in .git/config there is URL of 3rd repo as origin . But after push which outputted several objects in delta, I did not see those by git reflog on 2nd. Instead I saw in 2nd in refs/remotes/origin/main file hash of last commit pushed from 1st repo.

How do you think that happened? Maybe some internal `damage' to repo(s)? Other issues that lead me to investigate are in git fetch - "refuse", git pull "forced update, fetch updated current branch head". Local was 2 commits ahead of remote . TIA

git version 2.25.1

Added:

Yesterday repos seemed fine, I recall I first synced 1st and 2nd, then 2rd and 3nd, today I wanted to sync 1st and 2nd.

The only unusual thing I did I recall today after pull from 2nd to 1st there was a conflict, I did git reset FILE in 1st for file with that conflict and replaced (copied to repo folder) the file from backup outside of git.

Answer 1

git did what it was told to, push to origin HEAD:refs/remotes/origin/main , which is remote on remote.

When troubleshooting I noticed in .git/config entry for main was different, extra remotes . Apparently it set main to track main on remote's remote (further down the chain).

Also I recall I saw git-branch --set-upstream-to=main main produces effect of setting main branch to track origin's main and git-branch --set-upstream-to=origin/main main produce config change as described above. I was because I've made repo with git clone --mirror which sets refs translation in .git/config as fetch = +refs/*:refs/* whereas with regular clone : fetch = +refs/heads/*:refs/remotes/origin/* .

I think one needs to look attentively to output of the command to know the result.

To find out the cause of the issue included me running strace , seeing code only reads .git/config in user home, .git/config , .git/HEAD , .git/refs/heads/main and then realizing .git/config entry differs from entries for other repo (extra /remotes ).