Confused organizing git for Codeberg *and* Github #1931

Miq19 commented 2025年05月14日 17:36:24 +02:00

Comment

I am still in transition from Github to Codeberg, so I got some repositories still residing on Github, while others are on Codeberg already.

Now I created a new local repository for a project, developed for a while and now wanted to push it to Codeberg to create a new repo there - and miserably am failing at it.

What I did so far:

• did a git init
• added all files belonging to the repo
• made a git commit

But now when trying to push the project to Codeberg I am running into numerous issues.

git config --list gives me

credential.provider=generic
credential.helper=cache
credential.https://github.com.helper=!/usr/bin/gh auth git-credential
user.email=_my_mail_address_
credential.https://dev.azure.com.usehttppath=true
init.defaultbranch=main
core.repositoryformatversion=0
core.filemode=true
core.bare=false
core.logallrefupdates=true
remote.origin.url=https://Miq19@codeberg.org/Miq19/Bridge
remote.origin.fetch=+refs/heads/*:refs/remotes/origin/*

When I will do a git push -u origin master (was master by default, sorry) the system will hang forever until I Ctrl-C it.

I suppose the culprit is the credential.helper or credential.https, but what will I have to set to be able to sync to both Github and Codeberg?

Oh, by the way: I am using 2FA with an authenticator app to authenticate on Codeberg and Github.

### Comment I am still in transition from Github to Codeberg, so I got some repositories still residing on Github, while others are on Codeberg already. Now I created a new local repository for a project, developed for a while and now wanted to push it to Codeberg to create a new repo there - and miserably am failing at it. What I did so far: - did a ``git init`` - added all files belonging to the repo - made a ``git commit`` But now when trying to push the project to Codeberg I am running into numerous issues. ``git config --list`` gives me ``` credential.provider=generic credential.helper=cache credential.https://github.com.helper=!/usr/bin/gh auth git-credential user.email=_my_mail_address_ credential.https://dev.azure.com.usehttppath=true init.defaultbranch=main core.repositoryformatversion=0 core.filemode=true core.bare=false core.logallrefupdates=true remote.origin.url=https://Miq19@codeberg.org/Miq19/Bridge remote.origin.fetch=+refs/heads/*:refs/remotes/origin/* ``` When I will do a ``git push -u origin master`` (was ``master`` by default, sorry) the system will hang forever until I ``Ctrl-C`` it. I suppose the culprit is the ``credential.helper`` or ``credential.https``, but what will I have to set to be able to sync to both Github and Codeberg? Oh, by the way: I am using 2FA with an authenticator app to authenticate on Codeberg and Github.

Miq19 commented 2025年05月14日 18:11:42 +02:00

Solved it for now and for Codeberg only:

• created a personal access token
• created an empty repository with the matching name on the web interface
• git push -u origin master
• enter user name and access token in the pop-up dialog

I still would like to know how to use different, but global authentication for Github and Codeberg.

Solved it for now and for Codeberg only: - created a personal access token - created an empty repository with the matching name on the web interface - ``git push -u origin master`` - enter user name and access token in the pop-up dialog I still would like to know how to use different, but global authentication for Github and Codeberg.

berk76 commented 2025年05月14日 21:57:51 +02:00

Create two remotes:

git remote add codeberg https://Miq19@codeberg.org/Miq19/Bridge
git remote add github https://Miq19@github.com/Miq19/Bridge

and then

git push codeberg master
git push github master

Create two remotes: ``` git remote add codeberg https://Miq19@codeberg.org/Miq19/Bridge git remote add github https://Miq19@github.com/Miq19/Bridge ``` and then ``` git push codeberg master git push github master ```

Miq19 commented 2025年05月16日 15:06:18 +02:00

That would solve another issue - assessing the very same repository on Github and Codeberg.

My question was meant opposite:

• having a number of repositories on Github and another set on Codeberg
• all cloned locally into their own folders
• How is it possible to set the credentials globally for Github and Codeberg (2 sets) to not have to re-enter these again and again whenever pushing one of those repositories

Something like "If the local repository has a remote on Github, apply the Github credentials, if it resides on Codeberg, use the Codeberg ones".

Could I make myself better understandable now?

That would solve another issue - assessing the very same repository on Github and Codeberg. My question was meant opposite: - having a number of repositories on Github and another set on Codeberg - all cloned locally into their own folders - How is it possible to set the credentials *globally* for Github and Codeberg (2 sets) to not have to re-enter these again and again whenever pushing one of those repositories Something like "If the local repository has a remote on Github, apply the Github credentials, if it resides on Codeberg, use the Codeberg ones". Could I make myself better understandable now?

berk76 commented 2025年05月16日 19:13:23 +02:00

Basically there are two different protocols you can use for pulling and pushing your repositories (https and ssh). You are using https protocol but for scenario you described it seems ssh is more suitable.

I am not sure whether you are Linux, MacOS or Windows user.
If you are using linux or macos just open command line prompt. If you have Windows open gitbash.

Generate your private and public key pair (if you dont have it already)

ssh-keygen

Accept default location and you can provide short passphrase to protect your private key.
When your key pair is generated, open public key (file with *.pub extension) in any text editor and copy its content into clipboard.
Go to your Github/Codeberg settings into ssh / gpg keys menu and add new ssh key and copy content from your clipboard there.

Now you will use the same key for both Github and Codeberg.
If you have provided non-empty passphrase during key creation you will be allways prompted for it.

You can run this command to avoid prompting all the time

eval $(ssh-agent)
ssh-add

In case of ssh protocol you will need to use little bit different url format:

git remote add codeberg ssh://git@codeberg.org/Miq19/Bridge.git 
git remote add github ssh://git@github.com/Miq19/Bridge.git 

Basically there are two different protocols you can use for pulling and pushing your repositories (https and ssh). You are using `https` protocol but for scenario you described it seems `ssh` is more suitable. I am not sure whether you are Linux, MacOS or Windows user. If you are using linux or macos just open command line prompt. If you have Windows open gitbash. Generate your private and public key pair (if you dont have it already) ``` ssh-keygen ``` Accept default location and you can provide short passphrase to protect your private key. When your key pair is generated, open public key (file with *.pub extension) in any text editor and copy its content into clipboard. Go to your Github/Codeberg settings into `ssh / gpg keys` menu and add new ssh key and copy content from your clipboard there. Now you will use the same key for both Github and Codeberg. If you have provided non-empty passphrase during key creation you will be allways prompted for it. You can run this command to avoid prompting all the time ``` eval $(ssh-agent) ssh-add ``` In case of ssh protocol you will need to use little bit different url format: ``` git remote add codeberg ssh://git@codeberg.org/Miq19/Bridge.git git remote add github ssh://git@github.com/Miq19/Bridge.git ```

Miq19 commented 2025年05月17日 18:21:24 +02:00

@berk76 Thanks, that sounds like a slick solution.

I tried it and installed the ssh keys, but when trying to sync a repository on Codeberg (first I tried) I got

> git pull --tags origin main
fatal: couldn't find remote ref main

The main branch is named main.

[Edit] Found it, accidentially. Instead of git remote add codeberg ssh://... I need to name it git remote add origin ssh://...

@berk76 Thanks, that sounds like a slick solution. I tried it and installed the ssh keys, but when trying to sync a repository on Codeberg (first I tried) I got ``` > git pull --tags origin main fatal: couldn't find remote ref main ``` The main branch *is* named ``main``. [Edit] Found it, accidentially. Instead of ``git remote add codeberg ssh://... `` I need to name it ``git remote add origin ssh://...``

berk76 commented 2025年05月17日 20:17:04 +02:00

Bascally, you can have one or more remotes. Convention is that default one is named origin but it is not mandatory - you can name them as you want.

Bascally, you can have one or more remotes. Convention is that default one is named `origin` but it is not mandatory - you can name them as you want.