Codeberg/Community
54
325
Fork
You've already forked Community
12

Repo sync to GitHub fails because it asks for a username #1991

Closed
opened 2025年06月20日 14:00:21 +02:00 by Lampe2020 · 6 comments

Comment

I have set up a Codeberg repo to push its changes on push to a GitHub repo. I auth'd that with an SSH key (because GitHub disabled password auth), but when I try to sync the Codeberg changes up to GitHub it seems to ask Codeberg for a username, which it cannot provide since it is no interactive terminal but only a script pushing the changes. I cannot provide a username along with the SSH auth, so I feel like I'm stuck.
Is there a way to provide it with a GitHub username? Or can I push to GitHub in another way without manually needing to do so from my local repo clone?
screenshot of the error message

(I hope this is the right place to ask, because the description also mentions "platform-related issues")

### Comment I have set up a Codeberg repo to push its changes on push to a GitHub repo. I auth'd that with an SSH key (because GitHub disabled password auth), but when I try to sync the Codeberg changes up to GitHub it seems to ask Codeberg for a username, which it cannot provide since it is no interactive terminal but only a script pushing the changes. I cannot provide a username along with the SSH auth, so I feel like I'm stuck. Is there a way to provide it with a GitHub username? Or can I push to GitHub in another way without manually needing to do so from my local repo clone? ![screenshot of the error message](/attachments/e7571c9b-5759-46b7-8e9a-6f2d0bc7fc4b) (I hope this is the right place to ask, because the description also mentions "platform-related issues")
30 KiB

Hi, a few questions.

Did it work before? Or is this the first time trying to use push mirroring?
Could you verify that the public key that you obtain via "Copy public key" is added as a deploy key with write access on the target repository.

Hi, a few questions. Did it work before? Or is this the first time trying to use push mirroring? Could you verify that the public key that you obtain via "Copy public key" is added as a deploy key with write access on the target repository.

@Gusted wrote in #1991 (comment):

[...]
Did it work before? Or is this the first time trying to use push mirroring?

It did not work before as this is my first time even really using anything else than GitHub itself directly.

Could you verify that the public key that you obtain via "Copy public key" is added as a deploy key with write access on the target repository.

That might be part of the problem. I had added the key to my account as an SSH key, not to the repo as a deploy key.
I just deleted they key from my account and added it as a deploy key with write access to the GitHub repo, and tried to push the changes from Codeberg again, but it failed with the exact same error message. And yes, I checked that it actually tried to push the changes, the date and time match the point in time when I clicked the "Sync now" button.

@Gusted wrote in https://codeberg.org/Codeberg/Community/issues/1991#issuecomment-5610620: > [...] > Did it work before? Or is this the first time trying to use push mirroring? It did not work before as this is my first time even really using anything else than GitHub itself directly. > Could you verify that the public key that you obtain via "Copy public key" is added as a deploy key with write access on the target repository. That might be part of the problem. I had added the key to my account as an SSH key, not to the repo as a deploy key. I just deleted they key from my account and added it as a deploy key with write access to the GitHub repo, and tried to push the changes from Codeberg again, but it failed with the exact same error message. And yes, I checked that it actually tried to push the changes, the date and time match the point in time when I clicked the "Sync now" button.

It might be that the push mirror URL should be git@github.com/Lampe2020/L2KV.git instead, I don't think it transforms that automatically.

It might be that the push mirror URL should be `git@github.com/Lampe2020/L2KV.git` instead, I don't think it transforms that automatically.

When I try that it complains that I must not import local repos.
When I prefix that URL with HTTPS it instead fails to push because it cannot read the password for https://sanitized-credential@github.com.

When I try that it complains that I must not import local repos. When I prefix that URL with HTTPS it instead fails to push because it cannot read the password for `https://sanitized-credential@github.com`.

Ah so sorry, it needs to be prefixed with ssh://: ssh://git@github.com/Lampe2020/L2KV.git should work.

Ah so sorry, it needs to be prefixed with `ssh://`: `ssh://git@github.com/Lampe2020/L2KV.git` should work.

Yay, that fixed it! Thanks!
Thanks for being open to even my question that, knowing the answer, looks very dumb...
Of course it's SSH if I should use SSH auth, duh!

Yay, that fixed it! Thanks! Thanks for being open to even my question that, knowing the answer, looks very dumb... Of course it's SSH if I should use SSH auth, duh!
Sign in to join this conversation.
No Branch/Tag specified
main
No results found.
Labels
Clear labels
accessibility

Reduces accessibility and is thus a "bug" for certain user groups on Codeberg.
bug

Something is not working the way it should. Does not concern outages.
bug
infrastructure

Errors evidently caused by infrastructure malfunctions or outages
Codeberg

This issue involves Codeberg's downstream modifications and settings and/or Codeberg's structures.
contributions welcome

Please join the discussion and consider contributing a PR!
docs

No bug, but an improvement to the docs or UI description will help
duplicate

This issue or pull request already exists
enhancement

New feature
infrastructure

Involves changes to the server setups, use `bug/infrastructure` for infrastructure-related user errors.
legal

An issue directly involving legal compliance
licence / ToS

involving questions about the ToS, especially licencing compliance
please chill
we are volunteers

Please consider editing your posts and remember that there is a human on the other side. We get that you are frustrated, but it's harder for us to help you this way.
public relations

Things related to Codeberg's external communication
question

More information is needed
question
user support

This issue contains a clearly stated problem. However, it is not clear whether we have to fix anything on Codeberg's end, but we're helping them fix it and/or find the cause.
s/Forgejo

Related to Forgejo. Please also check Forgejo's issue tracker.
s/Forgejo/migration

Migration related issues in Forgejo
s/Pages

Issues related to the Codeberg Pages feature
s/Weblate

Issue is related to the Weblate instance at https://translate.codeberg.org
s/Woodpecker

Woodpecker CI related issue
security

involves improvements to the sites security
service

Add a new service to the Codeberg ecosystem (instead of implementing into Gitea)
upstream

An open issue or pull request to an upstream repository to fix this issue (partially or completely) exists (i.e. Gitea, Forgejo, etc.)
wontfix

Codeberg's current set of contributors are not planning to spend time on delegating this issue.
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Codeberg/Community#1991
Reference in a new issue
Codeberg/Community
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?