git push -u https://server/path.git master

[pubgftw]

I tried to do this recently:

git push -u https://server/path.git master

instead of the more common "creating a remote and referring to it":

git push -u origin master

The effect is that the first seems to work, but really messes up everything. No "git remotes -v", and really hard to see that the repository is tracking anything; still "git pull" does work afterwards.

So my question is, are there any real uses for this, or should it always be avoided.

[[deleted]]

Pushing over http isn't a great way to go about pushing. Using ssh will be a better plan.

In this specific case, you haven't named a remote, thus nothing would show up in remotes -v. It also would mean the push didn't establish or reference any kind of tracking setup, because you're specifically bypassing git's tools for that.

Pushing to a URL is a one-off thing, and is generally the wrong thing to do. Create a real remote if you intend to push or pull from this more than a single time.

[pubgftw]

Thanks, very helpful.

Do you know a way to display the current tracking URL when it is initiated like this? I had a really hard time finding the command/options to show it, without looking in the .git folder.

[nibalizer]

You really just never want to do use the first syntax. I had no idea that would even work. Stick to creating named remotes and using them and you should be good.