From: Petr Bena <petr@bena.rocks>
To: git@vger.kernel.org
Subject: Unable to change remote url of origin
Date: Wed, 27 Mar 2019 13:25:27 +0100 [thread overview]
Message-ID: <7b30ebfd-4f85-0fa7-8e66-7e63d7cb52d9@bena.rocks> (raw)
Hello,
I used to change remote URL simply by editing .git/config (which may not
be most correct way), but out of sudden I am no longer able to do that.
So I decided to do it the "proper way" but still - to no avail. Here is
what I do and also it's visible what is wrong:
# Display remote URL
petr.bena@MacBook:~/Documents/grumpy$ git remote -v
origin git@github.com:grumpy-irc/grumpy (fetch)
origin git@github.com:grumpy-irc/grumpy (push)
#Now change it to HTTPS instead of SSH
petr.bena@MacBook:~/Documents/grumpy$ git remote set-url origin
https://github.com/grumpy-irc/grumpy
# Verify if it has changed
petr.bena@MacBook:~/Documents/grumpy$ git remote -v
origin git@github.com:grumpy-irc/grumpy (fetch)
origin git@github.com:grumpy-irc/grumpy (push)
It's still SSH. What am I doing wrong?
petr.bena@MacBook:~/Documents/grumpy$ git --version
git version 2.21.0
petr.bena@MacBook:~/Documents/grumpy$ cat .git/config
[core]
repositoryformatversion = 0
filemode = true
bare = false
logallrefupdates = true
ignorecase = true
precomposeunicode = true
[submodule]
active = .
[remote "origin"]
url = https://github.com/grumpy-irc/grumpy
fetch = +refs/heads/*:refs/remotes/origin/*
[branch "master"]
remote = origin
merge = refs/heads/master
[submodule "src/libgp"]
url = http://github.com/grumpy-irc/libgp
[submodule "src/libirc"]
url = http://github.com/grumpy-irc/libirc
[branch "remote_scripts"]
remote = origin
merge = refs/heads/remote_scripts
next reply other threads:[~2019-03-27 12:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-27 12:25 Petr Bena [this message]
2019-03-27 12:57 ` Unable to change remote url of origin Kevin Daudt
2019-03-27 13:01 ` Petr Bena
2019-03-27 18:55 ` Andreas Schwab
2019-03-28 9:05 ` Petr Bena
2019-03-28 11:57 ` Petr Bena
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7b30ebfd-4f85-0fa7-8e66-7e63d7cb52d9@bena.rocks \
--to=petr@bena.rocks \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).