Codeberg/Documentation

Watch

Fork 169

More details about auth / credentials for pushing, and for pulling private repos #778

New issue

Open

opened 2026-04-20 00:59:00 +02:00 by Gouvernathor · 4 comments

Gouvernathor commented

2026-04-20 00:59:00 +02:00

The available information doesn't seem explicit enough to me, as it pertains to the following question : How can I set things up so that I'm not asked to authenticate when I pull from a private repository or when I push ? (As is the case when using github or gitlab.)

I'm currently seeing a behavior where push actions often fail and then either ask me to reauthorise through the browser, or it works the second time I try. The issue with the documentation is that it gives me contradictory answers.

The install git page, section Windows / Install / 3, states that if you use Git/Windows Credentials Managers, you will need to auth once and then be done with it :

the Git Credential Manager Core will be used by default. The Git Credential Manager can still be installed and used, but is now deprecated. When using either of these, your Git/Codeberg credentials will be stored in Windows' Credential Manager when you enter them for your first pull/push […] If you'd prefer not to store your credentials in Windows but e.g. in a password manager, select the third option (None). You'll have to enter your credentials at every push/pull.

However, the commit and push tutorial states that if you use HTTPS rather than SSH you will still need to enter your credentials each time :

The last step is to synchronize (push) the commit from the local repository to the remote one on Codeberg.
If you are using HTTPS, you will be asked for your Codeberg username and password. If you want to avoid entering your password every time, consider using SSH instead.

The available information doesn't seem explicit enough to me, as it pertains to the following question : _How can I set things up so that I'm not asked to authenticate when I pull from a private repository or when I push ?_ (As is the case when using github or gitlab.) I'm currently seeing a behavior where push actions often fail and then either ask me to reauthorise through the browser, or it works the second time I try. The issue with the documentation is that it gives me contradictory answers. [The install git page](https://docs.codeberg.org/getting-started/install-git/), section Windows / Install / 3, states that if you use Git/Windows Credentials Managers, you will need to auth once and then be done with it : > the Git Credential Manager Core will be used by default. The Git Credential Manager can still be installed and used, but is now deprecated. When using either of these, your Git/Codeberg credentials will be stored in Windows' Credential Manager when you enter them for your first pull/push […] If you'd prefer not to store your credentials in Windows but e.g. in a password manager, select the third option (None). You'll have to enter your credentials at every push/pull. However, [the commit and push tutorial](https://docs.codeberg.org/git/clone-commit-via-cli/#push) states that if you use HTTPS rather than SSH you will still need to enter your credentials each time : > The last step is to synchronize (push) the commit from the local repository to the remote one on Codeberg. > If you are using HTTPS, you will be asked for your Codeberg username and password. If you want to avoid entering your password every time, consider using SSH instead.

Gusted commented

2026-04-22 00:07:37 +02:00

Owner

@Gouvernathor wrote in #778 (comment):

However, the commit and push tutorial states that if you use HTTPS rather than SSH you will still need to enter your credentials each time :

This assumes you didn't setup a credential manager, it doesn't introduce credential managers here to avoid introducing too much at once..

Now, I'm not sure if that's a issue at all and I'm not sure how this relates to your issue that your credential manager is not working?

@Gouvernathor wrote in https://codeberg.org/Codeberg/Documentation/issues/778#issue-4458105: > However, [the commit and push tutorial](https://docs.codeberg.org/git/clone-commit-via-cli/#push) states that if you use HTTPS rather than SSH you will still need to enter your credentials each time : This assumes you didn't setup a credential manager, it doesn't introduce credential managers here to avoid introducing too much at once.. Now, I'm not sure if that's a issue at all and I'm not sure how this relates to your issue that your credential manager is not working?

Gouvernathor commented

2026-04-22 01:14:25 +02:00

Author

Well, I don't know whether it relates or not because it's not clear to me what the nominal behavior and workflow is.

So, if it said

The last step is to synchronize (push) the commit from the local repository to the remote one on Codeberg.
If you are using HTTPS, you will be asked for your Codeberg username and password (unless it is handled by a credential manager). If you want to avoid entering your password every time, consider using SSH instead.

it would be correct ?

If so, I would advise adding this sort of precision.

Still if so, then the git credential manager is at fault on my end, on two computers running Windows 11, exhibiting the exact same behavior, and on which github worked without issue for several years.

Well, I don't know whether it relates or not because it's not clear to me what the nominal behavior and workflow is. So, if it said > The last step is to synchronize (push) the commit from the local repository to the remote one on Codeberg. > If you are using HTTPS, you will be asked for your Codeberg username and password **_(unless it is handled by a credential manager)_**. If you want to avoid entering your password every time, consider using SSH instead. it would be correct ? If so, I would advise adding this sort of precision. --- Still if so, then the git credential manager is at fault on my end, on two computers running Windows 11, exhibiting the exact same behavior, and on which github worked without issue for several years.

Gouvernathor commented

2026-04-22 11:31:58 +02:00

Author

Issue 2541 describes the issue with the credentials itself, but I do think the documentation would deserve even a few words of disambiguation.

[Issue 2541](https://codeberg.org/Codeberg/Community/issues/2541) describes the issue with the credentials itself, but I do think the documentation would deserve even a few words of disambiguation.

Gusted commented

2026-04-27 16:44:56 +02:00

Owner

@Gouvernathor wrote in #778 (comment):

it would be correct ?

Yes, that would be okay to add.

@Gouvernathor wrote in https://codeberg.org/Codeberg/Documentation/issues/778#issuecomment-13522253: > it would be correct ? Yes, that would be okay to add.

No milestone

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/Documentation#778

No description provided.

Rows
Columns