Git "Mirroring" - Studio vs Git CLI

I think I have found that Studio does not support multiple git “push” URLs. Something like this:

[core]
	repositoryformatversion = 0
	filemode = false
	bare = false
	logallrefupdates = true
	symlinks = false
	ignorecase = true
[remote "origin"]
	url = https://SeanPI:<api key>@bitbucket.org/mycompany/gitmultipleremotes.git
	fetch = +refs/heads/*:refs/remotes/origin/*
	pushurl = https://SeanPI:<api key>@bitbucket.org/mycompany/gitmultipleremotes.git
	pushurl = https://devops.azure.com/<folder area>/Emerging%20Technology/_git/GitMultipleRemotes
[branch "origin"]
	remote = origin
	merge = refs/heads/origin

What is interesting is within Studio it shows the Bitbucket as it primary remote as that is from the “git remote add origin” command and the URL value above. The pushurls are not visible in Studio. If you use Studio commit/push, the Azure DevOps repo is what gets updated and not the Bitbucket repo.

Making repeatedly commit/push in Studio all work but to the Azure DevOps repo.

From the command line, running “git push origin” mirrors/resyncs the Bitbucket repo with all the commits pushed to the Azure DevOps repo making them match.

If the CLI is used for all Git commands, like commit/push, both repos are both updated like mirroring should be done.

They reason for attempting this, is on my project using Azure DevOps we have had one or two cases of Azure corrupting our repos.

There is no solution here … just commenting.

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.