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

[translate] "could not read Username" when pushing from translate to repository #2135

Open
opened 2025年09月15日 04:36:03 +02:00 by bobbens · 6 comments

Comment

When trying to push from the translation repository to the code repository, I get the following error:

 Could not push Naev/Naev: fatal: could not read Username for 'https://codeberg.org': terminal prompts disabled (128) 

I've tried setting it to use ssh instead, but it gives a different error.

For the record, it seems to read and pull from the git repository fine, it just can't seem to push. It also was imported from weblate.org instead of created directly on codeberg, so it may have somehow pulled some other settings or something. However, I can't see any way to change the username.

I've attached the settings as an image.

### Comment When trying to push from the [translation repository](https://translate.codeberg.org/projects/naev/naev/) to the [code repository](https://codeberg.org/naev/naev), I get the following error: ``` Could not push Naev/Naev: fatal: could not read Username for 'https://codeberg.org': terminal prompts disabled (128) ``` I've tried setting it to use ssh instead, but it gives a different error. For the record, it seems to read and pull from the git repository fine, it just can't seem to push. It also was [imported from `weblate.org`](https://codeberg.org/Codeberg/Community/issues/2129) instead of created directly on codeberg, so it may have somehow pulled some other settings or something. However, I can't see any way to change the username. I've attached the settings as an image.

Hi, it seems you have specified your a push repository. This means you will need to make the @translate user a collaborator on the repository with write access.

Hi, it seems you have specified your a push repository. This means you will need to make the @translate user a collaborator on the repository with write access.
Author
Copy link

@translate has been added but I get exactly the same message. It doesn't seem to be about lack of permissions, but something internal.

My hypothesis (probably wrong) is that when you create the project via codeberg, it adds some configuration file with the user information. However, since I imported from weblate.org instead, it is lacking the configuration file and thus doesn't know what user to use. Furthermore, it seems like this configuration is not exposed so I can't do anything to modify it.

@translate has been added but I get exactly the same message. It doesn't seem to be about lack of permissions, but something internal. My hypothesis (probably wrong) is that when you create the project via codeberg, it adds some configuration file with the user information. However, since I imported from weblate.org instead, it is lacking the configuration file and thus doesn't know what user to use. Furthermore, it seems like this configuration is not exposed so I can't do anything to modify it.

That's strange, I've looked around it nothing seems off to me. Changing it to make a PR instead of directly pushing to the main branch does work... naev/naev#2992

That's strange, I've looked around it nothing seems off to me. Changing it to make a PR instead of directly pushing to the main branch does work... https://codeberg.org/naev/naev/pulls/2992
Author
Copy link

The only thing I can think of is some git settings being wrong (ref: https://stackoverflow.com/questions/22147574/github-fatal-could-not-read-username-for-https-github-com-no-such-file-o ).
Maybe the PR works because it uses HTTPS POST instead of git command line? I would guess the issue would be a missing .git/config and git not being configured on a global level, but that's just an educated guess.

The only thing I can think of is some git settings being wrong (ref: https://stackoverflow.com/questions/22147574/github-fatal-could-not-read-username-for-https-github-com-no-such-file-o ). Maybe the PR works because it uses HTTPS POST instead of git command line? I would guess the issue would be a missing `.git/config` and git not being configured on a global level, but that's just an educated guess.

I poked around and bit and we were able to resolve this by using an SSH Repository push URL.

I'm not quite sure why that works when we didn't change any permissions for the @translate user, but I'm glad it's working nonetheless 😃

I poked around and bit and we were able to resolve this by using an SSH Repository push URL. I'm not quite sure why that works when we didn't change any permissions for the @translate user, but I'm glad it's working nonetheless 😃

@bobbens
Did you eventually get it working?
I'm running into the same problem.
Thanks in advance.

@bobbens Did you eventually get it working? I'm running into the same problem. Thanks in advance.
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
4 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#2135
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?