gitx remotes do not sync with .git/config

[rvwoens]

It seems as if gitx is keeping a separate remotes list. Manual changes to the config are not reloaded into gitx. It seems to me that gitx should use the config as its source, and not keep a separate remotes database by itself.

[Uncommon]

I don't think GitX is keeping any separate data. Can you give a specific example?

[kezabelle]

I'm experiencing, I think, a similar thing in 0.8.2 (and having just upgraded, 0.8.4)

if I do git remote add <name> git://github.com/whatever at the command line, it doesn't seem to take in GitX; that is, origin or whatever is there, but the new remotes aren't added, even at application restart. Attempting to add the remote via GitX errors with a notification that the remote already exists (correct).

If I git remote rm <name> and then add it via GitX, it is added successfully to both the GitX sidebar, and to the remote list as verified by git remote

Using $ git --version git version 1.7.6
via brew: $ brew info git git 1.7.6 http://git-scm.com /usr/local/Cellar/git/1.7.6 (1073 files, 20M) *

[dgm]

I have a similar situation, but I have a remote in gitx that is no longer tracked by git, and an additional one in git that gitx doesn't show!

Wait, the remote name in git/config was staging but it referenced a refs of a different name, which is what gitx was showing.